linux-kernel - Re: [PATCH] ip2: use request

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4856CB61.6030202@garzik.org>
Date:	Mon, 16 Jun 2008 16:21:53 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	David Woodhouse <dwmw2@...radead.org>,
	linux-kernel@...r.kernel.org, jaswinder@...radead.org
Subject: Re: [PATCH] ip2: use request_firmware()

Alan Cox wrote:
>> There is no reason why firmware must be artificially separated into 
>> firmware/
> 
> It seems a good step towards kicking it all out of the kernel tree into
> user space where it belongs.

Why does that goal need a toplevel directory in the kernel source tree, 
one that ultimately must mirror the other hierarchies already in the tree?

It's better to have drivers/char/ip2.ihex and keep everything related to 
a single driver in one place.

Extracting the firmware:  good

Scattering a /single/ driver across multiple directories in the kernel 
tree:  bad

	Jeff



--
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/