From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: James Simmons <jsimmons@infradead.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Andrew Morton <akpm@osdl.org>
Subject: Re: Re: Patch for review and testing
Date: Wed, 28 Jan 2004 11:18:00 +1100 [thread overview]
Message-ID: <1075249079.5655.229.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.44.0401272255180.19265-100000@phoenix.infradead.org>
On Wed, 2004-01-28 at 09:59, James Simmons wrote:
> P.S.
> Have any idea to know which card is the primary one on intel. I have
> been trying to figure that one out for quite some time.
AFAIK, we need the arch/i386 PCI probe code to "remember", when probing,
which VGA card had the IO enable bit set. There can be only one, the primary
one since BIOSes only POST one card.
BTW. What about my set of patches ? Did you have time to have a look ?
Ben.
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-01-28 0:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1075188083.6191.181.camel@gaston>
2004-01-27 20:07 ` Patch for review and testing James Simmons
2004-01-27 21:40 ` Benjamin Herrenschmidt
2004-01-27 22:09 ` James Simmons
2004-01-27 22:17 ` Benjamin Herrenschmidt
2004-01-27 22:59 ` James Simmons
2004-01-28 0:18 ` Benjamin Herrenschmidt [this message]
2004-01-28 1:01 ` Benjamin Herrenschmidt
2004-01-28 1:05 ` Benjamin Herrenschmidt
2004-01-29 19:53 ` Cursor patch James Simmons
2004-01-29 20:20 ` Andrew Morton
2004-01-30 23:54 ` New fb.h header James Simmons
2004-02-01 0:49 ` Andrew Morton
2004-02-01 1:03 ` Benjamin Herrenschmidt
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=1075249079.5655.229.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=geert@linux-m68k.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.