linux-kernel - Re: [POWER] battery calibration parameters from sysfs

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:	Fri, 4 Dec 2009 11:34:25 +0000
From:	Alexander Clouter <alex@...riz.org.uk>
To:	linux-kernel@...r.kernel.org
Cc:	linux-embedded@...r.kernel.org
Subject:  Re: [POWER] battery calibration parameters from sysfs

Linus Walleij <linus.walleij@...ricsson.com> wrote:
> 
> [snipped]
> 
> Is probably not very elegant. (Or is it?) Would it be permissible to
> pass in a table like:
> 
> cat >/sys/.../v_vs_cap <<EOF
> x0,y0
> x1,y1
> x2,y2
> EOF
> 
> And have the kernel parse x,y pairs up to EOF?
> 
> Or would it be preferable to do this thing by creating some
> misc device node like /dev/battery0 and a custom ioctl()?
> 
> Or is there some other way I haven't thought of?
> 
Although I'm a 'nobody' I would probably go for:
----
echo x0,y0:x1,y1:....
----

Pairs are seperated by ':' whilst values with ','.  I guess you could 
just use comma's all the way but I personally say that reduces 
readability...also means that maybe one day you want to pass only one or 
three values...the format could still work.

Easy to parse, a one liner, no fixed length, fits in with the existing 
use, etc etc.

Cheers

-- 
Alexander Clouter
.sigmonster says: You'll be sorry...

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