From: cinap_lenrek@gmx.de
To: 9fans@9fans.net
Subject: Re: [9fans] Thinkpad T61 Installation Experience
Date: Wed, 16 May 2012 18:34:06 +0200 [thread overview]
Message-ID: <a426ffee0671f828ca7e7ced67b98533@rei2.9hal> (raw)
In-Reply-To: <D2A5C7470D67A54FACE86B838946D49D14E466F7D0@NJ4MSGSCR02.markit.partners>
its a hexdump of the machines mp table. if you boot with *dumpmp=, the
kernel will dump its mp table to the console where it can be captured
from /dev/kmesg or other means like serial console.
normally, mp table is provided by the bios and placed in some memory
area where the kernel can find it. it basicly describes the machines
interrupt configuration, what busses there are, what processors ect.
the problem we had was that on sl's machine, the mptable just gives
us some legacy isa irq mapping. what we did was booting linux
(which uses acpi instead of mp table to acquire this information),
extracting the real interrupt mapping from dmesg and building a
fixed mp table that contains the real pci irq map.
with that, the irq sharing problems with usb are gone.
--
cinap
next prev parent reply other threads:[~2012-05-16 16:34 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 12:24 Burton Samograd
2012-05-16 12:32 ` Bruce Ellis
2012-05-16 12:49 ` Burton Samograd
2012-05-16 13:00 ` Peter A. Cejchan
2012-05-16 14:43 ` Martin Harriss
2012-05-16 15:00 ` Skip Tavakkolian
[not found] ` <CAJSxfmLZE3aNGmMusb=ZJAwn1AZEHuDxCeXJrRLADn+WV0KUEw@mail.gmail.c>
2012-05-16 15:02 ` erik quanstrom
2012-05-16 16:06 ` Charles Forsyth
2012-05-16 13:14 ` David du Colombier
2012-05-16 13:23 ` sl
2012-05-16 16:19 ` Burton Samograd
2012-05-16 16:34 ` cinap_lenrek [this message]
2012-05-17 12:39 ` Burton Samograd
2012-05-17 13:12 ` Jack Norton
2012-05-17 13:29 ` Burton Samograd
2012-05-17 14:01 ` erik quanstrom
2012-05-17 15:37 ` cinap_lenrek
2012-05-17 15:45 ` Burton Samograd
2012-05-17 16:00 ` cinap_lenrek
2012-05-18 21:13 ` [9fans] The creepy WORM. (was: Re: Thinkpad T61 Installation Experience) Nemo
2012-05-18 22:22 ` Bakul Shah
2012-05-18 22:45 ` Francisco J Ballesteros
2012-05-20 3:13 ` Bakul Shah
2012-05-20 8:37 ` Charles Forsyth
2012-05-20 8:38 ` Charles Forsyth
2012-05-20 10:07 ` Francisco J Ballesteros
2012-05-17 15:48 ` [9fans] Thinkpad T61 Installation Experience erik quanstrom
[not found] ` <D2A5C7470D67A54FACE86B838946D49D14E466F852@NJ4MSGSCR02.markit.pa>
2012-05-17 15:57 ` erik quanstrom
2012-05-17 16:09 ` David Romano
2012-05-17 16:26 ` erik quanstrom
2012-05-17 19:43 ` [9fans] +t and bind (Was Re: Thinkpad T61 Installation Experience) David Romano
2012-05-18 14:48 ` Ethan Grammatikidis
[not found] ` <CAM8pOuM+TDRPjkiWPENr_5qA0Mi5R=-ytmQSA1_ruUmQ54YbGw@mail.gmail.c>
2012-05-17 13:11 ` [9fans] Thinkpad T61 Installation Experience erik quanstrom
2012-05-17 13:28 ` Burton Samograd
2012-05-17 14:08 ` erik quanstrom
2012-05-17 14:49 ` Burton Samograd
2012-05-16 13:51 ` Nicolas Bercher
2012-05-16 14:05 ` erik quanstrom
2012-05-16 14:25 ` Charles Forsyth
2012-05-16 14:31 ` David du Colombier
[not found] ` <CAOw7k5jBKN2bxUov=Dagn1aL6nA_OORN+G8iPnkOzvf8mbScyw@mail.gmail.c>
2012-05-16 14:34 ` erik quanstrom
2012-05-16 14:18 ` David du Colombier
2012-05-16 14:21 ` cinap_lenrek
2012-05-16 14:36 ` erik quanstrom
2012-05-16 13:44 ` Nicolas Bercher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a426ffee0671f828ca7e7ced67b98533@rei2.9hal \
--to=cinap_lenrek@gmx.de \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).