From: yhlu <yhlu.kernel@gmail.com>
To: James Simmons <jsimmons@infradead.org>
Cc: "Daniël Mantione" <daniel@deadlock.et.tudelft.nl>,
"Jim Ramsay" <jim.ramsay@gmail.com>,
alex.kern@gmx.de, "Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: Atyfb questions and issues
Date: Mon, 15 Aug 2005 13:39:36 -0700 [thread overview]
Message-ID: <86802c440508151339790da3b2@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0508151741510.7300@pentafluge.infradead.org>
last year some time, I have manually the patch from 2.4 to 2.6. my
patch result is the same as 2.4. It only works when bios doesn't do
the init. Then if the BIOS do the init, it will hang there. I assume
something only can be done once.
YH
On 8/15/05, James Simmons <jsimmons@infradead.org> wrote:
>
> > james,
> >
> > I remember that xlinit in 2.6 kernel only works when BIOS option-rom
> > really init fb.
> > It can not work if the BIOS option rom is not executed.
> >
> > For 2.4, it reversed, it can not work if BIOS opton-rom is executed.
> > Only work if BIOS don't excute the option rom.
>
> You are right. The init_from_bios is called on x86 in aty_setup_generic
> before aty_init which calls the biosless initialization. The question is
> what needs to be done to properly fix it?
>
>
next prev parent reply other threads:[~2005-08-15 20:39 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 [this message]
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
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=86802c440508151339790da3b2@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=alex.kern@gmx.de \
--cc=daniel@deadlock.et.tudelft.nl \
--cc=jim.ramsay@gmail.com \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.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