linux-kernel - Re: [PATCH] i2c: i2c-tiny-usb: Add parameter for optional i2c-devices.

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:	Wed, 14 Nov 2012 00:41:58 +0100
From:	Alexander Holler <holler@...oftware.de>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	linux-kernel@...r.kernel.org, linux-i2c@...r.kernel.org,
	Till Harbaum <till@...baum.org>
Subject: Re: [PATCH] i2c: i2c-tiny-usb: Add parameter for optional i2c-devices.

Am 13.11.2012 23:42, schrieb Alan Cox:
> On Tue, 13 Nov 2012 21:52:20 +0100
> Alexander Holler <holler@...oftware.de> wrote:
>
>> Make it possible to define i2c-devices at the kernel command line
>> or as a module parameter.
>>
>> Format is devname1@...r1,devname2@...r2,...
>
> Why not do this with your initrd, you can deal with your rtc
> before mounting the real root fs.

I almost never use an initrd. Most of the time it isn't necessary and is 
just a waste of time to build, maintain and use it.

Thanks to git, I even find it it easier to maintain my own set of 
patches for the kernel (which I do since several years) and I find it 
easier to explain such others too, than to explain someone about how to 
build, maintain and use an initrd.

Regards,

Alexander
--
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/