Date: Fri, 30 Jan 2009 01:25:11 -0800 From: Julian Elischer <julian@elischer.org> To: Ed Schouten <ed@80386.nl> Cc: Alexander Leidinger <Alexander@Leidinger.net>, Daniel Lannstrom <op@trekdanne.se>, FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: Mackbook pro nvidia based video backlight Message-ID: <4982C777.9030700@elischer.org> In-Reply-To: <20090130084421.GO17198@hoeg.nl> References: <20090130085227.957230z897u8viww@webmail.leidinger.net> <20090130084421.GO17198@hoeg.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Ed Schouten wrote:
> * Alexander Leidinger <Alexander@Leidinger.net> wrote:
>>> The ideal solution would be to integrate it into vidcontrol, calling
>>> some kind of ioctl on the TTY/consolectl, but syscons is too brainless
>>> to know anything about hardware specific features.
>> Here we are back to what was proposed instead of sysctl. I have to admin
>> that I'm confused now about what you propose as a good solution.
>
> Well, I wouldn't like it if we create character devices, just to let it
> implement a single ioctl() ("/dev/backlight", for example). There is
> only 1 parameter that's adjustable, namely the backlight intensity. A
> sysctl is a good place to store such things.
I don't know.... you could flash morse code in response to a write.
>
> In my opinion we should only use character devices for devices that
> have the semantics of a file descriptor, namely to read/write data to
> it, perform select(), etc. Saying sysctl is bad, because it doesn't
> allow any permissions should be considered to be a defect of sysctl, not
> an advantage of devfs.
>
> The reason why I prefer consolectl, is because it already exists and
> allows related graphics parameters to be configured.
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4982C777.9030700>