public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Robert W. Fuller" <fullerrw@uindy.edu>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: TI Yenta socket Fish Please Report
Date: Wed, 27 Apr 2005 02:08:57 -0500	[thread overview]
Message-ID: <426F3A89.3010702@uindy.edu> (raw)

Hola,

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?

Thanks.

             reply	other threads:[~2005-04-27  7:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-27  7:08 Robert W. Fuller [this message]
2005-04-27  7:31 ` TI Yenta socket Fish Please Report Jonas Oreland
2005-04-27 23:31   ` Robert W. Fuller
2005-04-28  5:34     ` Robert W. Fuller
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=426F3A89.3010702@uindy.edu \
    --to=fullerrw@uindy.edu \
    --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