From: "Robert W. Fuller" <orangemagicbus@sbcglobal.net>
To: "Robert W. Fuller" <orangemagicbus@sbcglobal.net>
Cc: Jonas Oreland <jonas.oreland@mysql.com>,
"Robert W. Fuller" <fullerrw@uindy.edu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: TI Yenta socket Fish Please Report
Date: Thu, 28 Apr 2005 00:34:41 -0500 [thread overview]
Message-ID: <427075F1.8030009@sbcglobal.net> (raw)
In-Reply-To: <427020DA.4030504@sbcglobal.net>
Robert W. Fuller wrote:
> Jonas Oreland wrote:
>
>> Robert W. Fuller wrote:
>>>
>>> Looks like I have the same problem that was discussed here in
>>> February with PCI resources being assigned to the same range as RAM.
>>> This is the old thread: "IBM Thinkpad G41 PCMCIA problems [Was: Yenta
>>> TI: ... no PCIinterrupts. Fish. Please report.]" I'm having this
>>> problem on 2.6.11.
>>>
>>> Did the patch for this ever make it into the main kernel? Is it
>>> still in the -mm tree? Will it ever be in the main kernel? How do I
>>> figure these things out? Is there some bug database I can check?
>>>
>> I think it made it somehow.
>> I have a G40 which had the problem before I upgraded to 2.6.11
>
> Did it make it in for x86_64 kernel I wonder?
Hello. Is there anybody out there? Anybody who actually knows
something about what is in what kernel? Does anybody know how to figure
this out? Is there some kind of Bugzilla database or something I can
look at?
next prev parent reply other threads:[~2005-04-28 5:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-27 7:08 TI Yenta socket Fish Please Report Robert W. Fuller
2005-04-27 7:31 ` Jonas Oreland
2005-04-27 23:31 ` Robert W. Fuller
2005-04-28 5:34 ` Robert W. Fuller [this message]
2005-04-28 11:22 ` Russell King
2005-04-28 7:12 ` Dominik Brodowski
-- strict thread matches above, loose matches on Subject: below --
2005-04-27 7:09 Robert W. Fuller
2005-04-27 7:09 ` Robert W. Fuller
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=427075F1.8030009@sbcglobal.net \
--to=orangemagicbus@sbcglobal.net \
--cc=fullerrw@uindy.edu \
--cc=jonas.oreland@mysql.com \
--cc=linux-kernel@vger.kernel.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