Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Andy Walker <squawker@start.no>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Helge Deller <deller@gmx.de>, Matthew Wilcox <willy@debian.org>,
	Andy Walker <squawker@start.no>,
	parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] Status report - B132L and 725/100
Date: Tue, 18 Dec 2001 07:59:40 +0100 (CET)	[thread overview]
Message-ID: <1008658780.3c1ee95cb7432@nyepost.start.no> (raw)
In-Reply-To: <20011218004926.A5571@solo.franken.de>

Quoting Thomas Bogendoerfer <tsbogend@alpha.franken.de>:

> On Mon, Dec 17, 2001 at 11:21:01PM +0100, Helge Deller wrote:
> > I think a better solution would be to sort the found graphic devices
> by the hpa.
> [...]
> > In case the user wants to override with the sti= parameter the kernel
> should now
> > select this entry (e.g. sti=1 should select the card at 0xf4000000).
> 
> the big problem is, that stifb completly ignores sti= from the
> commandline
> and video=map doesn't seem to work (I need to reconfigure a machine to
> test
> that myself, which I hadn't time yet). The best thing would be to use
> the console path from pdc, no idea how hard that is.

I agree with Thomas here. The PDC console path should always be mapped to
fb0 if possible. How we order the other frambuffers is of less importance,
but the average user shouldn't need to play around with kernel parameters
to make the machine boot sensibly.

> It's probably not a big deal to use the default sti (sti=) for stifb,
> but I'd prefer either a video="???" solution or the pdc console path. If we
> decide on a solution, I'm going to implement it (if nobody else wants
> to do it :-)).
> 
> Thomas.

I'll certainly help with any testing I can - can't promise too many programming
hours right now though, unfortunately :(

-Andy

------------------------------------------------------------
Få din egen @start.no-adresse gratis på http://www.start.no/

  reply	other threads:[~2001-12-18  7:09 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
2001-12-17 22:21   ` Helge Deller
2001-12-17 23:49     ` Thomas Bogendoerfer
2001-12-18  6:59       ` Andy Walker [this message]
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=1008658780.3c1ee95cb7432@nyepost.start.no \
    --to=squawker@start.no \
    --cc=deller@gmx.de \
    --cc=parisc-linux@parisc-linux.org \
    --cc=tsbogend@alpha.franken.de \
    --cc=willy@debian.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