From: Jim Ramsay <jim.ramsay@gmail.com>
To: yhlu <yhlu.kernel@gmail.com>
Cc: "Daniël Mantione" <daniel@deadlock.et.tudelft.nl>,
alex.kern@gmx.de, "Linux Kernel" <linux-kernel@vger.kernel.org>,
"James Simmons" <jsimmons@infradead.org>
Subject: Re: Atyfb questions and issues
Date: Mon, 15 Aug 2005 10:25:14 -0600 [thread overview]
Message-ID: <4789af9e050815092545fe2925@mail.gmail.com> (raw)
In-Reply-To: <86802c4405081211021e76349c@mail.gmail.com>
On 8/12/05, yhlu <yhlu.kernel@gmail.com> wrote:
> I played a while with atyfb in LinuxBIOS. move the xl_init.c into LinuxBIOS.
>
> there is one patch call xlinit.c that can be used even ati fb is not
> inited in BIOS to make kernel still can use atyfb.
>
> I wonder if James put that in mainstream, he already sent one patch
> for 2.6.5....
>
> please refer to
> http://www.linuxbios.org/pipermail/linuxbios/2004-May/007734.html
It appears to me that this patch is in the 2.6.11 from linux-mips.org
that I am presently using.
> I guess the mips fw already execute the ati option rom via x86 emulator...
Maybe his mips FW does this, but mine doesn't. Any tips on how I can
do this in software?
--
Jim Ramsay
"Me fail English? That's unpossible!"
next prev parent reply other threads:[~2005-08-15 16:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-12 17:11 Atyfb questions and issues Jim Ramsay
2005-08-12 17:24 ` Daniël Mantione
2005-08-12 17:50 ` James Simmons
2005-08-12 18:15 ` yhlu
2005-08-15 16:43 ` James Simmons
2005-08-15 20:39 ` yhlu
2005-08-15 20:51 ` Jim Ramsay
2005-08-15 21:15 ` Daniël Mantione
2005-08-12 18:02 ` yhlu
2005-08-15 16:25 ` Jim Ramsay [this message]
2005-08-15 16:40 ` James Simmons
2005-08-15 19:21 ` Jim Ramsay
2005-08-15 19:40 ` Daniël Mantione
2005-08-15 20:53 ` Jim Ramsay
[not found] <4789af9e050815133711481beb@mail.gmail.com>
2005-08-15 21:10 ` Daniël Mantione
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=4789af9e050815092545fe2925@mail.gmail.com \
--to=jim.ramsay@gmail.com \
--cc=alex.kern@gmx.de \
--cc=daniel@deadlock.et.tudelft.nl \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yhlu.kernel@gmail.com \
/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