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]

Message-ID: <20081027085414.GH11339@tekkaman>
Date:	Mon, 27 Oct 2008 09:54:14 +0100
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 Thu, Oct 23, 2008 at 08:37:33AM -0700, Greg KH wrote:

> And again, you can still use sysfs for that as well.  I was just
> referring to the binary sysfs file that you use for the firmware
> download, it would make more sense for you to use the standard kernel
> firmware download interface instead of rolling your own here.

If I well understand the firmware class it works starting the firmware
download from the kernel side, that is into the kernel we should call
request_firmware() and then the files will
/sys/class/firmware/xxx/{loading,data} appear.

This solution doesn't fit C2 port needs since the firmware download is
decided from userland erasing and then writing into the
microcontroller on-board flash.

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/