Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: Andy Walker <squawker@start.no>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] Status report - B132L and 725/100
Date: Mon, 17 Dec 2001 14:35:13 +0000	[thread overview]
Message-ID: <20011217143513.W10085@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <1008589643.3c1ddb4b75583@nyepost.start.no>; from squawker@start.no on Mon, Dec 17, 2001 at 12:47:23PM +0100

On Mon, Dec 17, 2001 at 12:47:23PM +0100, Andy Walker wrote:
> Both work fine, but the same weird thing with the frame buffer ordering
> occurred with the 725/100 as it did with the B132L last week. With the
> console set in the PDC to the built-in fb, the kernel starts to boot
> on that device, then finds the Coral first and continues to boot
> on that, calling it fb0. Setting the console in PDC to the Coral makes
> everything work properly - the system boots all the way on the Coral.

OK, we need to figure out how to order the fb devices properly.  Right
now, they're initialised in IO tree order.  On a gecko with a graphics
card in the expansion slot, the expansion grahics gets device 0 and the
inbuilt is device 1.  Clearly similar problems exist on other machines.

So could everyone who has two (or more!) graphics cards in their machine
send the two lines of dmesg which describe their graphics card in the
inventory / buswalk section, their machine type (B132, Gecko, etc)
and indicate whether or not it gets them in the right order currently.

Example (made up!):

4. Frobnitz Ultra Graphics (10) at 0xf8000000 [8/1], versions 0xa, 0x0, 0x77
13. Thunder II graphics GSA form (10) at 0xf4000000 [10/8], versions 0xa, 0x0, 0x77
J282, works

Thanks.

-- 
Revolutions do not require corporate support.

  parent reply	other threads:[~2001-12-17 14:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-17 11:47 [parisc-linux] Status report - B132L and 725/100 Andy Walker
2001-12-17 13:15 ` Andy Walker
2001-12-19 11:36   ` Richard Hirst
2001-12-19 14:15     ` Andy Walker
2001-12-19 16:56       ` Grant Grundler
2001-12-19 17:58         ` Michael S.Zick
2001-12-19 20:28         ` Andy Walker
2001-12-19 20:40           ` Grant Grundler
2001-12-19 21:03             ` Richard Hirst
2001-12-20 10:06               ` Andy Walker
2001-12-20 11:15                 ` Richard Hirst
2001-12-20 20:42                 ` Grant Grundler
2001-12-17 14:35 ` Matthew Wilcox [this message]
2001-12-17 22:21   ` Helge Deller
2001-12-17 23:49     ` Thomas Bogendoerfer
2001-12-18  6:59       ` Andy Walker
2001-12-19 23:30 ` Richard Hirst

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=20011217143513.W10085@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --cc=parisc-linux@parisc-linux.org \
    --cc=squawker@start.no \
    /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