From: Chris Boot <bootc@bootc.net>
To: Jim Cromie <jim.cromie@gmail.com>
Cc: kernel list <linux-kernel@vger.kernel.org>,
soekris-tech@lists.soekris.com
Subject: Re: [Soekris] [RFC][PATCH] LED Class support for Soekris net48xx
Date: Sat, 08 Jul 2006 16:48:57 +0100 [thread overview]
Message-ID: <44AFD3E9.8050209@bootc.net> (raw)
In-Reply-To: <44AFCADA.6050805@gmail.com>
Jim Cromie wrote:
> Chris Boot wrote:
>> Hi all,
>>
>> After many years using Linux and hanging about on LKML without having
>> done much actual kernel hacking, I've decided to have a go! The module
>> below adds LED Class device support for the Soekris net48xx Error LED.
>> Tested only on a net4801, but should work on a net4826 as well. I'd
>> love to find a way of detecting a Soekris net48xx device but there is
>> no DMI or any Soekris-specific PCI devices.
>>
>> The patch is attached because Thunderbird kills tabs.
>>
> FWIW, the vintage scx200_gpio driver manipulates the LED just fine.
>
> # cat /etc/modprobe.d/gpio
> # assign last 2 dynamic devnums to gpio (255..240)
> options scx200_gpio major=240
> options pc8736x_gpio major=241
>
> soekris:~# ll /dev/led
> crw-r--r-- 1 root root 240, 20 Jun 24 2005 /dev/led
>
> echo 1 > /dev/led
>
>
> Is this insufficient ?
It works indeed very well, and this driver actually uses the scx200_gpio module
to do its work. But no it isn't enough, since this code ties into the existing
LED framework and can do nice built-in functionality like blinking according to
a timer, IDE disk activity, and a heatbeat-style load indicator. For free.
Chris
--
Chris Boot
bootc@bootc.net
http://www.bootc.net/
next prev parent reply other threads:[~2006-07-08 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-08 9:29 [RFC][PATCH] LED Class support for Soekris net48xx Chris Boot
2006-07-08 15:10 ` [Soekris] " Jim Cromie
2006-07-08 15:48 ` Chris Boot [this message]
2006-07-09 10:21 ` Chris Boot
2006-07-23 3:21 ` Eric Lammerts
2006-07-23 13:46 ` Chris Boot
2006-07-26 1:34 ` Eric Lammerts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44AFD3E9.8050209@bootc.net \
--to=bootc@bootc.net \
--cc=jim.cromie@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=soekris-tech@lists.soekris.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.