From: "Ville Syrjälä" <syrjala@sci.fi>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: bk fbdev-2.5 doesn't boot
Date: Fri, 7 May 2004 05:39:07 +0300 [thread overview]
Message-ID: <20040507023907.GA11790@sci.fi> (raw)
In-Reply-To: <200405022246.35720.alex.kern@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]
On Sun, May 02, 2004 at 10:46:35PM +0200, Alexander Kern wrote:
> Am Samstag, 1. Mai 2004 23:40 schrieb Ville Syrjälä:
> >
> > Does someone have an atyfb-only patch against mm?
> No, I wait for James website.
No matter. I just dropped the driver from fbdev-2.5 to mm and it seems to
work fine for the most part. I had to disable hw cursor because it oopsed
due to missing info->cursor.image.data. Just setting it to
cursor->image.data allowed me to boot but the cursor wasn't working right
so I just made it use the sw cursor instead.
Now my only problem is with XCLK on my Mobility. The BIOS inits the chip
to use ~63 MHz XCLK but atyfb claims that the BIOS tables specify 125 MHz.
The laptop in question is a HP OmniBook 6000 and there are two models:
full model with 125 MHz XCLK + 8MB SDRAM, and the crippled model with
XCLK cut in half + 4MB SDRAM (32-bit).
I have attached an XFree86 log with the BIOS dump if someone can figure
out if it contains something that would help autodetect the XCLK. If this
doesn't help I can bug my friend for the 125 MHz model BIOS dump for
comparison.
--
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/
[-- Attachment #2: x.log.bz2 --]
[-- Type: application/octet-stream, Size: 90679 bytes --]
next prev parent reply other threads:[~2004-05-07 2:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-01 21:40 bk fbdev-2.5 doesn't boot Ville Syrjälä
2004-05-02 20:46 ` Alexander Kern
2004-05-07 2:39 ` Ville Syrjälä [this message]
2004-05-18 0:10 ` 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=20040507023907.GA11790@sci.fi \
--to=syrjala@sci.fi \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).