Re: MGA driver question
Thomas Winischhofer wrote: Does the MGA driver initialize the card through int10 if it is secondary display adapter? Though I've not looked at it in a Millennium (pun), the last time I did, the BIOS was only read for the PINS (info structure). All setup was then done by the driver, not the BIOS, as it was a huge non-portable PITA to make a BIOS call. Besides, it allowed me to overclock the video memory a bit *evil grin* I assume the tradition was maintained for the decendents(?) -- Andrew E. Mileski ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Enabling mouse on X Server
Suresh wrote: Yes the OS is Linux, I am assuming the entries you have suggested should go into XF86Config or Xconfig files, but my port of X server don't have these files, What I have ported is Tiny X - Xfbdev Take a look at the kernel docs on mice for full details on the /dev/input/mice device node: Documentation/input -- Andrew E. Mileski ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Enabling mouse on X Server
Suresh wrote: I have ported X server on to my reference board based on Intel's Strong Arm, When I connected a USB optical wheel mouse to the USB port the mouse doesn't work: The mouse pointer appears on the screen, dmesg cmd also show that the system has identified the device (including details like manufacturer etc) But the GUI doesn't respond to the mouse. I even tried linking ln -s /dev/usb /dev/mouse but wouldn't work has anyone face this problem and any idea how to locate the issue. Thanks in Advance If Linux, you are using the wrong device. Section InputDevice Identifier Mouse0 Driver mouse Option Protocol IMPS/2 Option Device /dev/input/mice Option ZAxisMapping 4 5 Option Emulate3Buttons no EndSection -- Andrew E. Mileski ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Testing X on 2.6 Mega Hertz FPGA
Suresh Chandra Mannava wrote: Dear Friends, We are porting Xfree86 on to a new 32bit RISC processor. We have test FPGA system running at 2.6 Mega Hertz (Bogomips 0.16) on kernel 2.4.7. proposed system(ASIC) runs on ~300Mhz. My main concern is does Xfree86 can be tested on 2.6Mhz FPGA? What is the minimum clock speed required to run X? Which is the slowest clock speed system/processor that ran X applications? Our test system supports 2GB of RAM. I request your suggestions on feasibility of testing X on the above system. I've run XFree on a 33 MHz 80386 (Linux). It was slow, but it worked. It had a whopping 16 MB memory, and a 1 MB VGA video card. A closer comparison might be a 275 MHz StrongARM processor with 64 MB memory and a 2 MB video device (CyberPro 2000). Painful unaccelerated, but usable accelerated. Used as my office desktop for about 2 years, while I was developing on it. -- Andrew E. Mileski ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Testing X on 2.6 Mega Hertz FPGA
Andrew E. Mileski wrote: Suresh Chandra Mannava wrote: Dear Friends, We are porting Xfree86 on to a new 32bit RISC processor. We have test FPGA system running at 2.6 Mega Hertz (Bogomips 0.16) on kernel 2.4.7. proposed system(ASIC) runs on ~300Mhz. Ack! I read GHz there for some reason. Sorry. I don't think it will be very useful with stock XFree86. -- Andrew E. Mileski ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: You suggest an upgrade, eh?
François Puitg wrote: The symptoms are : after X has been started and window manager is up (it's the same with KDE, GNOME and twm), sometimes after 1 hour, but most of the time immediately, the keyboard freezes and the mouse becomes erratic, even when doing nothing, just standing there staring at the screen. Then, the machine doesn't respond anymore, neither to VT switching (obvious since the keyboard is dead), nor to ping. If you are really patient (the mouse is very slow), it's possible to exit the window manager : you have to move the mouse towards the exit button, wait to see it moving on thescreen, then click and the console is there. But now, the only solution is to reboot (with the reset switch). I don't mean to sound flip, but have you checked the fans lately? I've seen similar failures when the video card fan failed, and on another when the chipset fan failed. In both cases, the cooked chips were flaky and never fully functional again :( -- Andrew E. Mileski Ottawa, Canada http://isoar.ca/ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
