On Wed, Feb 13, 2013 at 5:11 PM, Arnaud Patard
<arnaud.pat...@rtp-net.org> wrote:
> "luke.leighton" <luke.leigh...@gmail.com> writes:
>
>> ok thanks marco.  does anyone know what this is referring to?  would
>> it be the accept4 syscall as shown in dmitri's patch:
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=68;filename=udev-182.patch;att=2;bug=648325
>
> according to git accept4 has been added into 2.6.36 and according to the
> squeeze changelog, it has been added into the 2.6.32-35 kernel.

 which unfortunately doesn't help anyone who has a dreamplug which
comes shipped as standard with a 2.6.32 <= .35 kernel.  especially on
learning that the default shipped kernel just works and on learning of
this dog's dinner mess don't want to go anywhere near a kernel
upgrade.

>>
>> this is a long-standing issue, it would be good to have it sorted out.
>
> If you're running debian kernels (the 3.2 from wheezy or any kernel
> newer than 2.6.32-35 on squeeze), it should already be fine. If you're
> running any other kernel, I don't see how it can be handled.

 it would seem that udev would have to dynamically work out "do i have
the accept4 function call, if so use it, if not then do what was being
done previously".

 or... just don't use accept4 at all.

> At least
> disabling the accept4 syscall for every kernels doesn't seem a good
> idea.

 i can't pretend to know what accept4 does, so can't say.

>>  i had to track down a suitable replacement kernel plus the
>> installation instructions, of course it's not a kernel from debian,
>> and the recommended one of course wifi didn't work.  i ended up here:
>> http://www.spinifex.com.au/plugs/dphowtowificl.html
>
> off-topic (it's not related to udev): if the wifi is not working, please
> check if it's working with newer kernels

 it's not. the exact reason's not clear yet.

 l.


-- 
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/capweedwvmxqti2nlgwzp28nwqesymqj_n50d4gjf9h37zsk...@mail.gmail.com

Reply via email to