From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: "David S. Miller" <davem@redhat.com>
Cc: viro@parcelfarce.linux.theplanet.co.uk, torvalds@osdl.org,
dancraig@internode.on.net, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test9-bk16 ALi M5229 kernel boot error
Date: Wed, 12 Nov 2003 18:06:42 +0300 [thread overview]
Message-ID: <20031112180642.A1064@jurassic.park.msu.ru> (raw)
In-Reply-To: <20031111225845.53d23a3a.davem@redhat.com>; from davem@redhat.com on Tue, Nov 11, 2003 at 10:58:45PM -0800
On Tue, Nov 11, 2003 at 10:58:45PM -0800, David S. Miller wrote:
> On Wed, 12 Nov 2003 04:31:34 +0000
> viro@parcelfarce.linux.theplanet.co.uk wrote:
> > Wrong fix, AFAICS. Original condition is bogus, no arguments here.
> > However, the point is
> > "tweak our southbridge only if northbridge is known to be OK with that"
> > and not
> > "tweak southbridge only if it's ours"
> >
> > IOW, proper check is || of those two.
>
> I agree with Al's analysis, and this is the kind of logic needed on
> sparc64 boxes as well.
I'm not sure there was any logic at all, given extremely misleading
comments in the original code. That "south-bridge's enable bit" stands
for "enable input pins for 80-conductor cable detection" according
to my (rather sparse) docs, and I don't understand why the hell it has
anything to do with a northbridge.
Someone with a more complete ALi documentation ought to verify that...
> Indeed, blindly deref'ing 'isa_dev' here was pretty bogus :)
Perhaps the source of this bug was the fact that M5229 controllers
are always part of the southbridge chip and therefore respective
"isa_dev" must exist. However, PCI IDs are re-writable on newer
ALi chips, which was probably the case.
Ivan.
next prev parent reply other threads:[~2003-11-12 15:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 2:46 Daniel Craig
2003-11-12 3:04 ` Linus Torvalds
2003-11-12 3:50 ` Jeff Garzik
2003-11-12 4:36 ` viro
2003-11-12 5:29 ` Linus Torvalds
2003-11-12 4:21 ` Daniel Craig
2003-11-12 4:31 ` viro
2003-11-12 6:58 ` David S. Miller
2003-11-12 15:06 ` Ivan Kokshaysky [this message]
2003-11-12 15:52 ` Linus Torvalds
2003-11-12 16:39 ` Ivan Kokshaysky
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=20031112180642.A1064@jurassic.park.msu.ru \
--to=ink@jurassic.park.msu.ru \
--cc=dancraig@internode.on.net \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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
all inboxes | Powered by JetHome®