netdev - Re: New driver "sfc" for Solarstorm SFC4000 controller.

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: <Pine.LNX.4.62.0805022004350.13626@dolphin.home>
Date:	Fri, 2 May 2008 20:10:53 +0100 (BST)
From:	Michael Brown <mbrown@...systems.co.uk>
To:	netdev@...r.kernel.org
Subject: Re: New driver "sfc" for Solarstorm SFC4000 controller.

On Thu, 1 May 2008, Andrew Morton wrote:
> >
> > ...
> >
> > --- /dev/null
> > +++ b/drivers/net/sfc/i2c-direct.h
> 
> There is no linkage with the kernel's own i2c layer?  Should there be?

Last time I checked (i.e. when I originally wrote this bit of the code), 
the kernel's own i2c layer didn't provide any clean way for kernel code 
(rather than user code) to access i2c devices.

As originally written, there was also a link to the kernel's i2c layer so 
that the NIC's onboard i2c bus could be exposed to e.g. lm_sensors for 
temperature monitoring.  I believe that this part of the driver was 
expunged since it made the patch "too large", but I may be wrong.

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