lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 07 Aug 2008 06:24:11 -0400
From:	Gene Heskett <gene.heskett@...il.com>
To:	Jaswinder Singh <jaswinder@...radead.org>
Cc:	martin@...inux.com, gareth@...inux.com, airlied@...ux.ie,
	dri-devel@...ts.sourceforge.net,
	LKML <linux-kernel@...r.kernel.org>,
	David Woodhouse <dwmw2@...radead.org>
Subject: Re: [PATCH] radeon_cp: use request_firmware

On Thursday 07 August 2008, Jaswinder Singh wrote:
>Moved datah before datal because datah is required before datal.
>
>Firmware blob looks like this...
>	__be32 datah
>	__be32 datal
>
>Signed-off-by: Jaswinder Singh <jaswinder@...radead.org>

When applied to 2.6.27-rc2, firmware/Makefile was rejected, so I manually added 
the blob list to that Makefile in what looked to be the correct place.  And added a
"make firmware_install" to my kernel builder script.

Unforch:
  MK_FW   firmware/R100_cp.bin.ihex.gen.S
make[1]: *** No rule to make target `firmware/R100_cp.bin.ihex', needed by `firmware/R100_cp.bin.ihex.gen.o'.  Stop.
make[1]: *** Waiting for unfinished jobs....
make: *** [firmware] Error 2

I suspect I need to go back and hand edit the .config to add the "radeon/"
in front of each of those, so its looking for
 "firmware/radeon/R100_cp.bin.ihex" in each of those cases.  Correct?  Or can
I use "radeon/*" ?

[...]

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Fiber optics caused gas main leak
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ