linux-kernel - Re: [PATCH 1/2] Add c2 port support.

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:	Thu, 23 Oct 2008 09:39:57 +0200
From:	Rodolfo Giometti <giometti@...eenne.com>
To:	Greg KH <greg@...ah.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] Add c2 port support.

On Wed, Oct 22, 2008 at 02:03:52PM -0700, Greg KH wrote:

> > Why is that good?  We have hundreds and hundreds of drivers which use a
> > device node interface and they work OK.
> > 
> > sysfs was never intended for use as the sole interface between device
> > drivers and userspace.  Using it that way is somewhat unconventional. 
> > At the very least I do think it needs more justification and
> > explanation than we're being provded here.
> 
> For firmware download to devices, using sysfs is the "normal" interface
> these days, that is what the firmware class is for.
> 
> Which reminds me, Rodolfo, why didn't you just use that interface for
> your firmware downloading instead of rolling your own here?

Because I need also to know revision ID, device ID and other minor
info from the microcontroller. Also I can reset the microcontroller
when I need it without downloading any new firmware.

Ciao,

Rodolfo

-- 

GNU/Linux Solutions                  e-mail: giometti@...eenne.com
Linux Device Driver                          giometti@...ux.it
Embedded Systems                     phone:  +39 349 2432127
UNIX programming                     skype:  rodolfo.giometti
--
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/