From: ebiederm@xmission.com (Eric W. Biederman)
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: James Simmons <jsimmons@infradead.org>,
Stian Jordet <liste@jordet.nu>,
Allan Duncan <allan.d@bigpond.com>,
linux-kernel@vger.kernel.org
Subject: Re: Linux 2.5.51
Date: 12 Dec 2002 08:01:42 -0700 [thread overview]
Message-ID: <m1n0nbuvqh.fsf@frodo.biederman.org> (raw)
In-Reply-To: <1039602072.3539.42.camel@zion>
Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:
> On Wed, 2002-12-11 at 10:25, Eric W. Biederman wrote:
> > > Well, I'm not sure it quite works yet. Maybe unaccelerated, but anyway,
> > > my version of radeonfb for 2.5 isn't accelerated yet anyway. I'll work
> > > on that (or Ani will) now that the API is stable enough.
> >
> > How well does this driver work if you don't have a firmware
> > driver initialize the card? aka a pci option ROM.
>
> Probably not at all
Well it was worth asking.
> > I am interested because with LinuxBIOS it is still a pain to run
> > PCI option roms, and I don't necessarily even have then if it a
> > motherboard with video. There are some embedded/non-x86 platforms
> > with similar issues.
>
> Well, at least r128's and radeon's need the memory controller and PLLs
> initialized by the BIOS/firmware, we don't have documentation about how
> to acheive that ourselves (and this can depend on the specific wiring of
> a given card anyway).
I believe those actions have to be taken. I haven't seen how flexible
the chips are with respect to which memory they take, which is
generally where most of the complexity comes in.
I have written northbridge memory initialization code that generally
does not depend on the motherboard, I would be very surprised to find
out that video card are generally more difficult (except in the area
of documentation).
> > My primary interest is in the cheap ATI Rage XL chip that is on many
> > server board. PCI Vendor/device id 1002:4752 (rev 27) from lspci.
> >
> > If nothing else if some one could point me to some resources on
> > how to get the appropriate documentation from the video chipset
> > manufacturers I would be happy.
> >
> > But I did want to at least point that running a system with out bios
> > initialized video was certainly among the cases that are used.
>
> This is not possible with most modern cards without specific POST code
> provided by the chip manufacturer.
Without documentation surely. Though for that aspect of things
I primarily care about the cheap controllers that are used for onboard
video. Which I suspect is a much simpler case to handle.
Eric
next prev parent reply other threads:[~2002-12-12 14:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 3:17 Linux 2.5.51 Linus Torvalds
2002-12-10 5:47 ` Allan Duncan
2002-12-10 6:49 ` James Simmons
2002-12-10 16:59 ` Benjamin Herrenschmidt
2002-12-10 16:58 ` Stian Jordet
2002-12-10 18:16 ` James Simmons
2002-12-10 19:18 ` Benjamin Herrenschmidt
2002-12-11 9:25 ` Eric W. Biederman
2002-12-11 10:21 ` Benjamin Herrenschmidt
2002-12-12 15:01 ` Eric W. Biederman [this message]
2002-12-23 14:56 ` Geert Uytterhoeven
2002-12-11 15:26 ` James Simmons
2002-12-12 15:02 ` Eric W. Biederman
2002-12-12 15:54 ` Richard B. Johnson
2002-12-23 15:00 ` Geert Uytterhoeven
2002-12-10 19:17 ` Benjamin Herrenschmidt
2002-12-10 18:12 ` James Simmons
2002-12-10 5:52 ` Linux 2.5.51 (fbcon issues) CaT
2002-12-10 6:52 ` James Simmons
2002-12-10 6:22 ` CaT
2002-12-10 18:24 ` James Simmons
2002-12-12 0:40 ` Linux 2.5.51 Matthew Dobson
-- strict thread matches above, loose matches on Subject: below --
2002-12-10 12:15 Petr Vandrovec
2002-12-10 22:18 ` James Simmons
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=m1n0nbuvqh.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=allan.d@bigpond.com \
--cc=benh@kernel.crashing.org \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liste@jordet.nu \
/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