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: Fri, 12 Aug 2005 11:15:26 -0700 [thread overview]
Message-ID: <86802c4405081211153ec42f7e@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0508121848040.30829@pentafluge.infradead.org>
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.
YH
On 8/12/05, James Simmons <jsimmons@infradead.org> wrote:
>
> > > I have the following issue. I am trying to get an ATI Rage XL chip
> > > working on a MIPS-based processor, with a 2.6.11-based kernel from
> > > linux-mips.org. Now, I know that this was working with a 2.4.25-based
> > > kernel previously.
> >
> > Okay, the 2.4 driver is more intrusive, it programs the chip from start as
> > much as possible, while the 2.6 driver tries to depend on Bios settings. I
> > haven't checked out the 2.6 driver enough to see if it is still possible
> > to program from scratch.
>
> The code is there to program the chip from scratch. Just select
>
> "Rage XL No-BIOS Init support"
>
> The last time I tried it it didn't work. If we could get it working that
> would be great.
>
> > Yes, according to my register data sheet a 7 means the memory clock
> > frequency is derived from DLLCLK. Unfortunately I don't know what this
> > DLLCLK is. I think it means the chip isn't properly initialized yet and it
> > clocks the memory from a safe clock source to allow the computer to start.
> >
> > However, we most likely have no way to find out the speed of this DLLCLK.
> >
> > The memory clock frequency is important for the driver to be able to set a
> > display mode; it needs to program a memory reload frequency into the chip
> > which depends on the memory frequency.
>
> Their is code in xlint.c that should properly set this. Have to debug that
> code.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2005-08-12 18:15 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 [this message]
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
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=86802c4405081211153ec42f7e@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