nanogui: Thread: Work on ARM?

Hello, Vasant:

  I've tried the microwin .87 version on BRUTUS, but not work.
After I boot-up Brutus with Arm-linux, and run the Nano-X, it
says: Cannot bind to named socket: Invalid argument. 

  And then I tried to run the bin/world directly('coz I opt
LINK_SERVER_WITH_APP Y), it's also erro. It says:
Error opening /dev/fb0: No such file or directory
Cannot initialise screen: No such file or directory
Cannot open graphics

  How to get a /dev/fb0??

  My arm linux version: 2.2.14, gcc-2.95.2, glibc-2.1.2,
binutils-2.9.5.0.22. Hope anybody can give me some clues.

  I change following setting of original microwin/src/config:

ARCH                     = LINUX-ARM
OPTIMIZE                 = N
SCREEN_PIXTYPE           = PF_TRUECOLOR332
LINK_APP_INTO_SERVER     = Y

FRAMEBUFFER              = Y
FBVGA                    = Y
VTSWITCH                 = Y
PORTRAIT_MODE            = N
NOMOUSE                  = Y

SA1100_LCD_LTLEND        = Y

:   And then I tried to run the bin/world directly('coz I opt
: LINK_SERVER_WITH_APP Y), it's also erro. It says:
: Error opening /dev/fb0: No such file or directory
: Cannot initialise screen: No such file or directory
: Cannot open graphics
: 
:   How to get a /dev/fb0??
: 
:   My arm linux version: 2.2.14, gcc-2.95.2, glibc-2.1.2,
: binutils-2.9.5.0.22. Hope anybody can give me some clues.

2.2.14 must be setup to support framebuffer.  The framebuffer
HOWTO is in microwin/src/INSTALL.  However, make sure
that you have the following set in your kernel .config, or /dev/fb0
can't be opened, which means you don't have a framebuffer:

CONFIG_FB=y
CONFIG_DUMMY_C ONSOLE=y
CONFIG_FB_xxx=y where xxx is your kernel hw for framebuffer support
CONFIG_FBCON_ADVANCED=y
and then the 
CONFIG_FBCON_CFB8=y and others to match your 
framebuffer resolution.

If your kernel isn't compiled right, /dev/fb0 open will fail,
just like you're getting.

Regards,

Greg

Eric,

I suspect your problem is even more straight forward than this. If you've
compiled your Kernel using the default configuration settings for the brutus
board;

ie. make brutus_config

then you will almost certainly have framebuffer suport.

What I suspect you need to do is create the framebuffer device before you
run your demos.

ie. mknod /dev/fb0 c 29 0

Of course, if you updated your Ramdisk you wouldn't need to do this each
time you want to use the framebuffer device. I would suggest you try this
before re-compiling your kernel.

Best Regards,

Sandy Weir

-----Original Message-----
From: Greg Haerr ####@####.####
Sent: Saturday, February 19, 2000 8:29 PM
To: ####@####.#### ####@####.####
Cc: ####@####.####
Subject: Re: Work on ARM?


:   And then I tried to run the bin/world directly('coz I opt
: LINK_SERVER_WITH_APP Y), it's also erro. It says:
: Error opening /dev/fb0: No such file or directory
: Cannot initialise screen: No such file or directory
: Cannot open graphics
: 
:   How to get a /dev/fb0??
: 
:   My arm linux version: 2.2.14, gcc-2.95.2, glibc-2.1.2,
: binutils-2.9.5.0.22. Hope anybody can give me some clues.

2.2.14 must be setup to support framebuffer.  The framebuffer
HOWTO is in microwin/src/INSTALL.  However, make sure
that you have the following set in your kernel .config, or /dev/fb0
can't be opened, which means you don't have a framebuffer:

CONFIG_FB=y
CONFIG_DUMMY_C ONSOLE=y
CONFIG_FB_xxx=y where xxx is your kernel hw for framebuffer support
CONFIG_FBCON_ADVANCED=y
and then the 
CONFIG_FBCON_CFB8=y and others to match your 
framebuffer resolution.

If your kernel isn't compiled right, /dev/fb0 open will fail,
just like you're getting.

Regards,

Greg


---------------------------------------------------------------------
To unsubscribe, e-mail: ####@####.####
For additional commands, e-mail: ####@####.####

> 
>   My arm linux version: 2.2.14, gcc-2.95.2, glibc-2.1.2,
> binutils-2.9.5.0.22. Hope anybody can give me some clues.
> 

Excuse me, cause my reply is a little out of topic.

Could you tell me how to buld the arm-toolchain successfully?

I use the following source, kernel 2.2.14, gcc 2.95.2, 
glibc-2.1.2, binutils-2.9.5.0.27.
The gcc and binutils are normally built.
However, when I build the glibc, the make process is out with
this error 
"/usr/local/arm/bin/ld: unrecognized emulation mode: elf32arm
Supported emulations: armelf_linux armelf_linux26 armelf"

Could anyone tell me why?

Thanks
 
kirk


_______________________________________________________________
http://www.SINA.com - #1 Destination Site for Chinese Worldwide