From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: rostedt@goodmis.org
Subject: Re: [PATCH -rt] Buggy uart (for 2.6.16)
Date: Mon, 10 Apr 2006 17:25:26 -0600 [thread overview]
Message-ID: <443AE966.8050203@shaw.ca> (raw)
In-Reply-To: <60bbB-6XU-17@gated-at.bofh.it>
Steven Rostedt wrote:
> I just found some more information. The board's chipset is an Intel
> 440BX. I think this is responsible for the uarts.
No, it would be whatever Super I/O chip is present on the board.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2006-04-10 23:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <604MF-5Tc-7@gated-at.bofh.it>
[not found] ` <6083V-2pi-9@gated-at.bofh.it>
[not found] ` <60bbB-6XU-17@gated-at.bofh.it>
2006-04-10 23:25 ` Robert Hancock [this message]
2006-04-10 13:37 [PATCH -rt] Buggy uart (for 2.6.16) Steven Rostedt
2006-04-10 16:53 ` Gunther Mayer
2006-04-10 17:51 ` Steven Rostedt
2006-04-10 20:22 ` Steven Rostedt
2006-04-11 20:57 ` Steven Rostedt
2006-04-12 6:27 ` Ingo Molnar
2006-05-07 8:30 ` Russell King
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=443AE966.8050203@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
/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