linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <syrjala@sci.fi>
To: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: URGENT: status of atyfb
Date: Wed, 4 Aug 2004 01:05:28 +0300	[thread overview]
Message-ID: <20040803220528.GA29548@sci.fi> (raw)
In-Reply-To: <1091568340.1900.14.camel@gaston>

On Wed, Aug 04, 2004 at 07:25:40AM +1000, Benjamin Herrenschmidt wrote:
> 
> Also, when just dropping the existing driver into the current linus tree, the
> cursor code is blowing up, I don't know why yet, I suppose some changes to the
> common code in the fbdev tree. I'll have a look.

I had (probably) the same oops when using the driver from bk on 2.6.5-mm6. 
Alex's latest patch fixed it for me.


On a somewhat related note...
I'd like to know if my LT LCD register access patch works correctly. It 
should allow the generic LCD code to work on LT. It's included in Alex's 
latest patch. But since parsing the BIOS is out of the question you'd have 
to hardcode the LCD parameters. Could you test it?

-- 
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/


-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com

  reply	other threads:[~2004-08-03 22:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-02  3:31 URGENT: status of atyfb Benjamin Herrenschmidt
2004-08-02  5:21 ` Benjamin Herrenschmidt
2004-08-03 20:57   ` Alexander Kern
2004-08-03 21:25     ` Benjamin Herrenschmidt
2004-08-03 22:05       ` Ville Syrjälä [this message]
2004-08-06  6:09       ` Alexander Kern
2004-08-06  8:10         ` Benjamin Herrenschmidt

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=20040803220528.GA29548@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).