see www.arm.linux.org.uk for supported pxa250 development boards
We had good luck with both the Accelent IDP and the Intel Lubbock
boards.
Bradley A. Singletary
Applications Developer
4Access Communications
Phone: (770)475-9060
Fax: (770)475-2485
On Thu, 29 Au
On Fri, 30 Aug 2002, Jonathan Amery wrote:
>Date: Fri, 30 Aug 2002 13:58:43 +0100
>From: Jonathan Amery <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED], debian-x@lists.debian.org
>Subject: Re: a small C program to test xdm's /dev/mem reading on your
>architecture
>
>In article <[EMAIL PROTECTED]> B
In article <[EMAIL PROTECTED]> Branden writes:
>> I can't believe he actually intends to keep it like this..
>I'm going to #define DEV_RANDOM /dev/random for Linux systems.
And Debian Hurd? Or does the Hurd not have /dev/random or /dev/urandom?
I suspect that /dev/urandom may be the better cho
In article <[EMAIL PROTECTED]> Kusti writes:
>I believe the /dev/mem gets read only in systems where no /dev/(u)random
>exists.
Actually, the standard configuration is that /dev/mem is read. The
code to read from /dev/(u)random isn't activated in any situation in
the standard upstream X distrib
[Apologies to readers of debian-sparc, who have already received a copy of this]
In article <[EMAIL PROTECTED]> [EMAIL PROTECTED] write:
[XDM randomness]
>/dev/random? /dev/urandom? You are kidding. This randmomness is used
>to create authorisation cookies for X which in my understanding provide
5 matches
Mail list logo