From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jon Smirl <jonsmirl@yahoo.com>
Cc: dri-devel <dri-devel@lists.sourceforge.net>,
fb-devel <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [Dri-devel] Rage128 and Radeon patches
Date: 14 Aug 2003 12:42:07 +0200 [thread overview]
Message-ID: <1060857726.602.53.camel@gaston> (raw)
In-Reply-To: <20030814034338.25567.qmail@web14907.mail.yahoo.com>
On Thu, 2003-08-14 at 05:43, Jon Smirl wrote:
> Hopefully these is the last versions. They implement:
Please CC me any further radeonfb patches, I have my own stuff
pending that I need to sync (and I sort of took over maintainership)
> 1) add every know PCI ID
> 2) access ROM directly instead of relying on copy in
> low RAM. This allows multiple cards. Required
> MPP_TB_CONFIG fix in driver.
This is a problem. We also parse it to find the DFP EDID and/or
flat panel informations, do that work with the real ROM ? I don't
know much about x86 BIOSes, but at least for the DFP EDID, I suppose
that one is read in RAM by the BIOS, not in the ROM...
> 3) implemented kernel 2.6 module parameters
> 4) Cleaned up error paths and made sure resources are
> released on errors. Both build without compiler
> warnings now. You can ins/rm mod multiple times
> without problem. Just don't do it from a window in
> your X server.
> 5) Driver marks both primary and secondary devices as
> being in use.
>
> These drivers are bigger than the old ones but that's
> because I added descriptions for the parameters and a
> bunch more error messages. Code is probably smaller.
> Strip the strings and remove unneeded entries from the
> device table for embedded systems.
>
> I don't own Apple hardware. Anyone want to make sure I
> didn't break Powerbooks?
You may want to look at the version I have in my tree
on ppc.bkbits.net/linuxppc-2.5-benh. I don't have much time
to sync with your before a couple of weeks for now... This version
rely on my Power Management stuffs I posted earlier that James didn't
seem to merge yet though.
> It would be nice if someone with Radeon documentation
> verified my chip IDs and family classifications. It is
> important that secondary devices are marked correctly
> in the driver. I did the best I could from Xfree
> source and PCI databases.
The ChipIDs aren't in the documentation. I suppose the best source
here is the XFree driver.
> Patches are against the current 2.6 kernel tree.
> Anyone want to volunteer to get these into the kernel?
>
>
> =====
> Jon Smirl
> jonsmirl@yahoo.com
>
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com
--
Benjamin Herrenschmidt <benh@kernel.crashing.org>
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
next prev parent reply other threads:[~2003-08-14 10:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-14 3:43 Rage128 and Radeon patches Jon Smirl
2003-08-14 10:42 ` Benjamin Herrenschmidt [this message]
2003-08-14 16:00 ` Re: [Dri-devel] " Jon Smirl
2003-08-14 22:04 ` Benjamin Herrenschmidt
2003-08-14 22:47 ` Jon Smirl
2003-08-15 8:18 ` Benjamin Herrenschmidt
2003-08-14 13:22 ` Alex Deucher
2003-08-14 17:13 ` [Linux-fbdev-devel] " Jon Smirl
2003-08-14 18:06 ` Alex Deucher
2003-08-14 18:32 ` Steven Newbury
2003-08-14 18:26 ` dri fb drivers [was: Re: Rage128 and Radeon patches] Otto Solares
2003-08-14 18:55 ` dri fb drivers [was: Re: [Linux-fbdev-devel] " Jon Smirl
2003-08-14 19:33 ` dri fb drivers [was: " James Simmons
2003-08-14 20:18 ` Otto Solares
2003-08-14 21:45 ` Re: dri fb drivers [was: Re: [Linux-fbdev-devel] " Jon Smirl
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=1060857726.602.53.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=dri-devel@lists.sourceforge.net \
--cc=jonsmirl@yahoo.com \
--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 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.