From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Thomas Unger <unger@informatik.uni-siegen.de>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: keylargo PCI USB controller nor enabled on G4 xserve
Date: Thu, 16 Sep 2004 01:06:12 +1000 [thread overview]
Message-ID: <1095260769.2665.471.camel@gaston> (raw)
In-Reply-To: <41485359.80602@informatik.uni-siegen.de>
On Thu, 2004-09-16 at 00:36, Thomas Unger wrote:
> looks to me like a pci problem as the device obviously isn't even
> enumerated. I tried several 2.6 versions, none of them fixed this.
>
> Has anyone had similar problems or even a solution to this?
> Any help is welcome.
There's something wrong with PCI enumeration on the Xserve G4 in 2.6,
though I haven't yet figured out what exactly. Ideally, I would need
to have physical access to one of these to fix it ... anybody in .au ?
Ben.
next prev parent reply other threads:[~2004-09-15 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 14:36 keylargo PCI USB controller nor enabled on G4 xserve Thomas Unger
2004-09-15 15:06 ` Benjamin Herrenschmidt [this message]
2004-09-17 1:25 ` Benjamin Herrenschmidt
2004-09-21 10:34 ` Thomas Unger
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=1095260769.2665.471.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=unger@informatik.uni-siegen.de \
/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