netdev - Re: [bug?] tg3: Failed to load firmware "tigon/tg3

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]

Date:	Mon, 07 Jul 2008 14:58:19 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	alan@...rguk.ukuu.org.uk
Cc:	jeff@...zik.org, dwmw2@...radead.org, andi@...stfloor.org,
	tytso@....edu, hugh@...itas.com, akpm@...ux-foundation.org,
	kosaki.motohiro@...fujitsu.com, mchan@...adcom.com,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	netdev@...r.kernel.org
Subject: Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin"

From: Alan Cox <alan@...rguk.ukuu.org.uk>
Date: Mon, 7 Jul 2008 22:14:27 +0100

> > > You seem to be trying to conflate legal and technical issues here.
> > 
> > Exactly like the patches we are current discussing.
> > 
> > Thanks for walking right into that. :-)
> 
> No - the patches are for technical reasons, 

Which are?  Consistent use of request_firmware()?

That's pure bullox as far as I can see.  Why provide the means to
do something nobody has had a need for in 6+ years?  Who needs
to load different firmware for the tg3 driver?

Who needs that capability? Distribution vendors?  What for?
In what case will they need to load different firmware from
what the driver maintainer tested as a unit?

Rather, they want separation.  I can see no other real impetus.

And, btw, who has the right to enforce this new burdon upon driver
maintainers when they have had a working and maintainable system for
so long?

I can only see it being about separation, pure and simple.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html