From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: fb-devel <linux-fbdev-devel@lists.sourceforge.net>
Subject: URGENT: status of atyfb
Date: Mon, 02 Aug 2004 13:31:37 +1000 [thread overview]
Message-ID: <1091417497.7393.63.camel@gaston> (raw)
Hi !
I'm having more and more pain with atyfb at this point. I really need
the changes that bring the pci_driver (and new PM callbacks) so I can
properly work on these.
However, bringing just that change from the fbdev tree to the main tree
is incredibly painful due to the major amount of changes that went into
this driver.
So can somebody show up and tell me what is the status of this driver as
it is currently in the fbdev-2.5 bk tree and if that stuff can actually
be sent upstream ASAP or not ?
I don't feel like re-doing just the pci_driver changes, did it once, was
painful enough, but on the other hand, this driver has been drifting
away from mainstream for ages, which is simply not acceptable.
Ben.
-------------------------------------------------------
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
next reply other threads:[~2004-08-02 3:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 3:31 Benjamin Herrenschmidt [this message]
2004-08-02 5:21 ` URGENT: status of atyfb Benjamin Herrenschmidt
2004-08-03 20:57 ` Alexander Kern
2004-08-03 21:25 ` Benjamin Herrenschmidt
2004-08-03 22:05 ` Ville Syrjälä
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=1091417497.7393.63.camel@gaston \
--to=benh@kernel.crashing.org \
--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).