From: Jim Ramsay <jim.ramsay@gmail.com>
To: yhlu <yhlu.kernel@gmail.com>
Cc: "James Simmons" <jsimmons@infradead.org>,
"Daniël Mantione" <daniel@deadlock.et.tudelft.nl>,
alex.kern@gmx.de, "Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: Atyfb questions and issues
Date: Mon, 15 Aug 2005 14:51:16 -0600 [thread overview]
Message-ID: <4789af9e050815135169a76799@mail.gmail.com> (raw)
In-Reply-To: <86802c440508151339790da3b2@mail.gmail.com>
On 8/15/05, yhlu <yhlu.kernel@gmail.com> wrote:
> 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.
That is exactly what I did in my proposed patch, attached earlier.
I noticed the same problem.
Does anyone out there know how you can tell if the RageXL chip has
already been initialized?
One test I have that works on my hardware is to test the STAT0
register. If it ends with 0x95, the chip has not been initialized,
otherwise I initialize it.
--
Jim Ramsay
"Me fail English? That's unpossible!"
next prev parent reply other threads:[~2005-08-15 20:51 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 [this message]
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=4789af9e050815135169a76799@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.