linux-kernel - preferred way of fw loading

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-next>] [day] [month] [year] [list]

Message-ID: <4547E720.4080505@gmail.com>
Date:	Wed, 01 Nov 2006 01:15:28 +0100
From:	Jiri Slaby <jirislaby@...il.com>
To:	Linux kernel mailing list <linux-kernel@...r.kernel.org>
CC:	R.E.Wolff@...Wizard.nl
Subject: preferred way of fw loading

Hello,

is preferred to have firmware in kernel binary (and go through array of chars)
or userspace (and load it through standard kernel api)?

For char sx driver in this case (I hope there is no later fw):
ftp://ftp.bitwizard.nl/specialix/sx_firmware_306c.tgz

Now it's 2 .c files used by loader through ioctl. After compilation it has:
   text    data     bss     dec     hex filename
      4    8416       2    8422    20e6 si2_z280.o
      4   19484       2   19490    4c22 si3_t225.o

So convert it to binary (and load it through userspace) or simply #include it in
the sources? I hope the former is preferred?

thanks,
-- 
http://www.fi.muni.cz/~xslaby/            Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E
-
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/