<html><body bgcolor="#FFFFFF"><div>Hello,</div><div><br></div><div>I have an 3D2 board which has a different BIOS. I'm running Voyage 0.6.5, that can explain your problem. <br><br>-- <div>Stéphane Acounis</div></div><div><br>Le 11 févr. 2011 à 16:54, Yago Fernandez Hansen <<a href="mailto:sti@soportec.com">sti@soportec.com</a>> a écrit :<br><br></div><div></div><blockquote type="cite"><div>
Hi everybody<br>
<br>
I have been reading your interesting posts to make tests with the configurations you have included.<br>
<br>
I have the folowing configuration:<br>
<br>
Alix.3d3 with last BIOS<br>
Voyage Linux 0.6.5<br>
<br>
I have soldered two cables to a pushbutton (normally open). <br>
The result is the next:<br>
<br>
<b>od -x /dev/cs5535_gpio24 | cut -c 11-12 | head -1</b><br>
<br>
always returns 30, pushed or not.<br>
I like the bash script Stephane uses, but what is the next step?<br>
<br>
Thank you again for your help.<br>
<br>
Yadox<br>
<br>
<br>
<blockquote type="CITE">
<pre>> The state of the button can be monitored with this line:
> od -x /dev/cs5535_gpio24 | cut -c 11-12 | head -1
>
> it reads 31 in the idle state and 30 if the button is pressed.
>
> --
> Stphane ACOUNIS
> SUBATECH Nantes - Service d'lectronique
> Tl: 02-51-85-84-28 06-64-62-99-20
>
> Faut pas se laisser abattre devise Kennedy
>
> _______________________________________________
> Voyage-linux mailing list
> <a href="mailto:Voyage-linux@list.voyage.hk"><a href="mailto:Voyage-linux@list.voyage.hk">Voyage-linux@list.voyage.hk</a></a>
> <a href="http://list.voyage.hk/mailman/listinfo/voyage-linux"><a href="http://list.voyage.hk/mailman/listinfo/voyage-linux">http://list.voyage.hk/mailman/listinfo/voyage-linux</a></a>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <a href="http://list.voyage.hk/pipermail/voyage-linux/attachments/20110210/433e57ea/attachment-0001.htm"><a href="http://list.voyage.hk/pipermail/voyage-linux/attachments/20110210/433e57ea/attachment-0001.htm">http://list.voyage.hk/pipermail/voyage-linux/attachments/20110210/433e57ea/attachment-0001.htm</a></a>
------------------------------
Message: 7
Date: Thu, 10 Feb 2011 14:47:13 +0100
From: St?phane Acounis <<a href="mailto:stephane.acounis@subatech.in2p3.fr"><a href="mailto:stephane.acounis@subatech.in2p3.fr">stephane.acounis@subatech.in2p3.fr</a></a>>
Subject: Re: [Voyage-linux] About GPIO support
To: <a href="mailto:voyage-linux@voyage.hk"><a href="mailto:voyage-linux@voyage.hk">voyage-linux@voyage.hk</a></a>
Message-ID: <20110210144713.087dfe7e@nanpc201>
Content-Type: text/plain; charset=ISO-8859-1
Le Thu, 10 Feb 2011 08:21:21 -0500
Jon Meek <<a href="mailto:meekjt@gmail.com"><a href="mailto:meekjt@gmail.com">meekjt@gmail.com</a></a>> a crit:
> Stphane - When you implement the power off button please post the
> details!
>
Ohhhh very simple, it works quite well. I have an Alix 3D2 board and
the switch is located near the USB connector (S1 written on the PCB).
Just solder two wires and connect them to a normally opened push button.
I have wrote a simple bash script (power-button):
------------------------------------------------------------------------------
#!/bin/bash
while true; do
button=`od -x /dev/cs5535_gpio24 | cut -c 11-12 | head -1`
if [ $button == "30" ]; then
sleep 3
button=`od -x /dev/cs5535_gpio24 | cut -c 11-12 | head -1`
if [ $button == "30" ]; then
beep -f 1000 -r 2 -n -r 5 -l 10 --new
/sbin/poweroff
else
exit
fi
fi
sleep 1
done
------------------------------------------------------------------------------
and installed a line in the root's crontab:
@reboot /data/Scripts/power-button
Then pressing more than 3 seconds on the switch will do a clean halt of
the board.
If someone has a better and more efficient way to monitor the switch, please share.
--
Stphane ACOUNIS
SUBATECH Nantes - Service d'lectronique
Tl: 02-51-85-84-28 06-64-62-99-20
Faut pas se laisser abattre devise Kennedy
------------------------------
Message: 8
Date: Thu, 10 Feb 2011 10:44:53 -0600
From: Jeff Ramin <<a href="mailto:jeff.ramin@singlewire.com"><a href="mailto:jeff.ramin@singlewire.com">jeff.ramin@singlewire.com</a></a>>
Subject: [Voyage-linux] bringing an interface up when it becomes
available
To: voyage-linux <<a href="mailto:voyage-linux@voyage.hk"><a href="mailto:voyage-linux@voyage.hk">voyage-linux@voyage.hk</a></a>>
Message-ID: <<a href="mailto:4D541605.1090000@singlewire.com"><a href="mailto:4D541605.1090000@singlewire.com">4D541605.1090000@singlewire.com</a></a>>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Is there a way to configure voyage such that an interface is automatically
brought up when the link state changes? For example, let's say the machine
boots but doesn't have a physical connection to the network. After boot,
an ethernet cable is connected.
How would I set things up so that the interface is brought up and configured
(or dhcp/pump run) without user interaction?
Thanks.
</pre>
</blockquote>
<br>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Voyage-linux mailing list</span><br><span><a href="mailto:Voyage-linux@list.voyage.hk">Voyage-linux@list.voyage.hk</a></span><br><span><a href="http://list.voyage.hk/mailman/listinfo/voyage-linux">http://list.voyage.hk/mailman/listinfo/voyage-linux</a></span><br></div></blockquote></body></html>