On Mon, Aug 24, 2009 at 3:58 AM, Ben Hutchings<b...@decadent.org.uk> wrote:
> Based on a patch by Jaswinder Singh Rajput . For Radeon 100- to 500-series,
> firmware blobs look like:
> struct { __be32 datah; __be32 datal; } cp_ucode[256];
>For Radeon 600-series, firmware blobs look like:
>__be32 pm4_ucode[PM4_UCODE_SIZE * 3];
> __be32 pfp_ucode[PFP_UCODE_SIZE];
>For Radeon 700-series, firmware blobs look like:
>__be32 pm4_ucode[R700_PM4_UCODE_SIZE];
> __be32 pfp_ucode[R700_PFP_UCODE_SIZE];
>Signed-off-by: Ben Hutchings --- This has been tested in Debian as a patch to
>2.6.30. Ben.
Something annoyed my reply formatting, but anyhoo, the mga and r128
patches are fine.
This patch has a few issues before I can put it into drm-next.
1. r600/r700 firmware probably should be split into two files, we have
more firmware
releases coming for another part of the chip, and I'm not sure how we can handle
merging or versioning if we put all 3 into one blob. Maybe Alex can comment on
AMDs preferred format.
2. KMS is merged, please enable KMS code in staging and make the firmware loader
work in r100.c (this kms driver is pretty much a completely separate
entity) so don't
share code.
Dave.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
