Subject:
RE: [nanogui] Re: how to debug microwindow
From:
Narasimha Reddy K ####@####.####
Date:
17 Mar 2002 13:17:43 -0000
Message-Id: <5575473D4532D411BE4C009027E8C838068E66A4@MASBLREXC02>
Could you please suggest for cutting down the XServer size from 1.7 MB to
atleast 1000 KB? We have tried a lot but could not able to succeed. I got
the info. from microwindows site that size of XServer came down from 2MB to
300KB. Please suggest which def file that needs to be disabled or is there
any alternative to reduce the size.
Regards,
N Reddy
-----Original Message-----
From: Greg Haerr ####@####.####
Sent: Friday, March 15, 2002 9:55 AM
To: Narasimha Reddy K; 'Hejinjing'
Cc: ####@####.####
Subject: Re: [nanogui] Re: how to debug microwindow
You'll need to use a C compiler that is supported
by the RTOS you're developing for. Consult your
RTOS developer's manual for information on how
to create executables from C source code and makefiles.
The Microwindows Project is not dependent on a
particular OS or makefile system, although we
provide working versions for GNU C and a few other
compilation systems.
Regards,
Greg
: Do I need to use separate compiler for any sort of RTOS(Real Time OS). Or
: same compiler supports.
: Can I make use of EXEs directly in any of the RTOS. Or Do I need to have
: some convertion utilty in order to achive the same functionality.
: pls. suggest.
:
: Regards,
:
: N Reddy
:
: -----Original Message-----
: From: Hejinjing ####@####.####
: Sent: Friday, March 15, 2002 6:48 AM
: To: Greg Haerr
: Cc: ####@####.####
: Subject: [nanogui] Re: how to debug microwindow
:
:
: It works now! I am very glad!
: Thank you and all!
:
: I think I can go the first step of 10000 steps
:
: Best Regards,
:
: Hejinjing
: ----- Original Message -----
: From: Greg Haerr
: To: Hejinjing
: Cc: ####@####.####
: Sent: Friday, March 15, 2002 1:31 AM
: Subject: Re: how to debug microwindow
:
:
: Also, telnet login in as an ordinary userl, then "su root"
:
: Regards,
:
: Greg
: ----- Original Message -----
: From: Hejinjing
: To: Greg Haerr
: Cc: ####@####.####
: Sent: Thursday, March 14, 2002 2:14 AM
: Subject: Re: how to debug microwindow
:
:
: Dear sir and all,
:
: Thanks for your help!
:
: when I use telnet from a separate terminal,I can only
: use ordinary USER-NAME to login and can not use "root"
:
: in scr_fb.c like next
: fb_open(PSD psd)
: {
: ...
: ...
: ...
: #if HAVETEXTMODE
: /* open tty, enter graphics mode*/
: tty = open ("/dev/tty0", O_RDWR); file://****************
: if(tty < 0) {
: EPRINTF("Error can't open /dev/tty0: %m\n");
: goto fail;
: }
: if(ioctl (tty, KDSETMODE, KD_GRAPHICS) == -1) { file://*************
:
: EPRINTF("Error setting graphics mode: %m\n");
: close(tty);
: goto fail;
: }
: close(tty);
: #endif
: ...
: ...
: ...
: fail:
: close(fb);
: return NULL;
: }
: if I open /dev/tty0, it says
: "Error can't open /dev/tty0: Permission denied"
:
: if I change open /dev/tty0 to /dev/tty
: it will says:
: "Error setting graphics mode: Invalid argument"
:
: Now, Two question:
: 1. can I telnet use root identifier ?
: 2. if can't, how to overcome these problem ?!
:
: I wonder how the supper man like Greg build the greate building !
:
: Best Regard!
:
: Hejinjing
:
: ----- Original Message -----
: From: Greg Haerr
: To: Hejinjing
: Sent: Thursday, March 14, 2002 10:41 AM
: Subject: Re: how to debug microwindow
:
:
: The best I can say is it sounds like you've got a kernel problem
: switching to or acessing the graphics framebuffer device. Again,
: I suggest telneting in from a seperate terminal, and then running
: "kbd_mode -a" to reset the keyboard.
:
: Regards,
:
: Greg
: ----- Original Message -----
: From: Hejinjing
: To: Greg's email
: Sent: Monday, March 11, 2002 10:32 PM
: Subject: Re: how to debug microwindow
:
:
: Dear Sir;
: Very glad and excited for you help.
: I change the config file to use the TTY driver,Yes ,It works,
: GDB can go through GdOpenKeyboard().
: but,when go to GdOpenScreen -> scr_fb.c -> fb_open() like
next,
:
: if(!(env = getenv("FRAMEBUFFER")))
: env = "/dev/fb0";
: fb = open(env, O_RDWR);
: if(fb < 0) {
: EPRINTF("Error opening %s: %m. Check kernel config\n", env);
: return NULL;
: }
: if(ioctl(fb, FBIOGET_FSCREENINFO, &fb_fix) == -1 ||
: ioctl(fb, FBIOGET_VSCREENINFO, &fb_var) == -1) {
: EPRINTF("Error reading screen info: %m\n");
: goto fail;
: }
:
: when trace to ioctl(...)function, systerm will die again! keyboard
: will not repones include
: (ALT_F1,ALT_F2...),but it can respones CAPSLOCK SCROLLOCK,you can
: also use CTRL_ALT_DEL to
: restart the computer.
:
: I have no idea except ask for your help again!
:
: With Best Regard!
:
: Mar 12,2002
: Hejinjing
:
: ----- Original Message -----
: From: Greg's email
: To: Hejinjing
: Sent: Tuesday, March 12, 2002 12:35 AM
: Subject: Re: how to debug microwindow
:
:
: The first thing I do is use the regular TTY driver, not the
: TTYSCAN
: driver, this will help. Edit the config file for this. Also, I
: sometimes
: debug using telnet from a different terminal, using gdb. This
: allows
: gdb text to be seen and the graphics at the same time. If
: Microwindows
: crashes, you have to run the Linux keyboard reset program,
: whose name I can't remember, I think it's "kbd_reset a" or
: something like that to use the console again. When I get home,
: I can find this for you if you like.
:
: Regards,
:
: Greg
: ----- Original Message -----
: From: Hejinjing
: To: ####@####.####
: Sent: Wednesday, March 06, 2002 10:06 PM
: Subject: how to debug microwindow
:
:
: Dear Sir;
: Very glad to meet you!
: I am a pupil on microwindow.
: Due to some reason, I need to cut out some context of
: microwindow.
: But when I use gdb to debug or trace
: nano-X->srvmain.c(gsinitial->gdopenkeyboard)->kbdtty_scan.c(
: TTY_open->ioctr), the linux system will halted,the
keyboard
: can not work,wrong echo char will display
: on screen when you type keyboard,you must press reset key
or
: power down computer to reload linux system.
: Can I use GDB to trace microwindow server? What must I do
?
: Please help me!
: Many Many thanks for your help !
:
: my e_mail is ####@####.####
:
: Mar 7,2002
: Hejinjing
:
:
:
: DISCLAIMER: Information contained and transmitted by this E-MAIL is
: proprietary to MASCOT SYSTEMS LTD and is intended for use only by the
: individual or entity to which it is addressed, and may contain information
: that is privileged, confidential or exempt from disclosure under
applicable
: law. If this is a forwarded message, the content of this E-MAIL may not
have
: been sent with the authority of the Company. If you are not the intended
: recipient, an agent of the intended recipient or a person responsible for
: delivering the information to the named recipient, you are notified that
any
: use, distribution, transmission, printing, copying or dissemination of
this
: information in any way or in any manner is strictly prohibited. If you
have
: received this communication in error, please delete this mail & notify us
: immediately at ####@####.#### Before opening attachments,
: please scan for viruses
:
:
:
: ---------------------------------------------------------------------
: To unsubscribe, e-mail: ####@####.####
: For additional commands, e-mail: ####@####.####
:
DISCLAIMER: Information contained and transmitted by this E-MAIL is
proprietary to MASCOT SYSTEMS LTD and is intended for use only by the
individual or entity to which it is addressed, and may contain information
that is privileged, confidential or exempt from disclosure under applicable
law. If this is a forwarded message, the content of this E-MAIL may not have
been sent with the authority of the Company. If you are not the intended
recipient, an agent of the intended recipient or a person responsible for
delivering the information to the named recipient, you are notified that any
use, distribution, transmission, printing, copying or dissemination of this
information in any way or in any manner is strictly prohibited. If you have
received this communication in error, please delete this mail & notify us
immediately at ####@####.#### Before opening attachments,
"Please scan for Viruses"
