On Fri, 15 Oct 1999, Philip Blundell wrote:
> >The only real difference between what I've done and what's on the Intel
> >site as far as GNU packages is that I'm using EGCS 1.1.2 and the
> >apropriate ARM patch from Phil. B as opposed to EGCS 1.1.1 and a patch.
>
> You should probably consider using gcc 2.95.1 now.
The problem is that my kernels crash quite rapidly if compiled with
gcc-2.95.x and I didn't got around to find the problem yet. No problem
with user space apps though.
> >I followed Intel's directoy conventions to the letter (I changed nothing).
>
> I think Intel's instructions are wrong; this has been discussed here recently.
> See the mailing list archives.
I have a tarball with my current working toolset binaries which is a
30-meg file.
I'll try to upload it to ftp.netwinder.org (don't know if I'm allowed to
however, anybody knows?). This contains egcs, glibc and all. This might
help starters...
> >If I wanted the output "console" (Linux login, etc) to appear on the LCD
> >would I have to write the LCD driver or is there something I can use to
> >get basic text on the screen? Anything for the keyboard IC (USAR
> >SPICoder)?
>
> I think there is a Brutus framebuffer driver now. Nico can probably give a
> more definite answer.
Yes there is.
Nicolas
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
