linux-kernel - Re: [PATCH RESEND] x86, intel

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: <20120410151529.5bcc5ce6@pyramind.ukuu.org.uk>
Date:	Tue, 10 Apr 2012 15:15:29 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	mingo@...e.hu, linux-kernel@...r.kernel.org
Subject: Re: [PATCH RESEND] x86, intel_mid: ADC management

> Could you be more specific about what this early boot time stuff is?
> Looking at the changelogs in there it all looks like the standard
> battery monitoring and power supply stuff that these ADCs get used for -
> just based on the changelogs there doesn't appear to be anything
> remarkable here.

It depends on the actual device but things the like battery management
are a key one.

> We can't just keep on going round adding new custom interfaces every
> time someone supports a new SoC - it means we end up having to sit and

We can't go around blocking entire platforms because of the IIO blob. I
raised this point with the whole previous *generation* of Intel SoC
devices about IIO and nothing has been done about it.

Get IIO out of staing and we can look at it, until then IIO is staging
code, it's not part of the kernel, it may never be part of the kernel,
and it should never block actual kernel code.

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