netdev - Re: SMC91x: forcing speed

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, 08 Jun 2009 18:17:21 -0400 (EDT)
From:	Nicolas Pitre <nico@....org>
To:	David Miller <davem@...emloft.net>
Cc:	mfuzzey@...il.com, richard.rojfors@...ian.se,
	netdev@...r.kernel.org
Subject: Re: SMC91x: forcing speed

On Mon, 8 Jun 2009, David Miller wrote:

> From: Martin Fuzzey <mfuzzey@...il.com>
> Date: Mon, 08 Jun 2009 23:42:47 +0200
> 
> > IMHO the place for board specific hacks is in the board specifc startup
> > code - am I wrong?
> 
> We never add bootup time hacks for things that already have
> a suitable generic and clean configuration interface.

Maybe suitable in a workstation setup.

> People ask for module options and all kinds of crap like that
> to set link parameters, and we always say no.

And this is probably why there is still a disconnect between mainline 
and embedded people.

For some systems, the simple notion of a special ramdisk just makes the 
whole thing 4 times more complex.

Wouldn't it be possible to accommodate those people with a generic 
ethtool module that simply interpret some kernel cmdline parameters in a 
uniform and maintainable way to apply some settings during kernel boot?

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