Software Development and Consulting
Posts tagged ‘linux’
The driver is supplied ready to be inserted into the linuxppc-2.4-devel tree.
The driver has so far been tested on a small number of systems and with a small number of I2C parts. Thanks to Gleb Natapov, Matthew S. McClintock, and others for testing. Further test results are welcome.
Continue reading ‘MPC107 I2C Driver’ »
These are experimental Linux 2.2 and 2.4 framebuffer drivers for the Asiliant 69030 graphics chip. This chip was previously available from Intel, and is descended from a Chips and Technologies part. The 2.2 driver is thus based on the Linux chipsfb.c driver, which supports the 65555 part in certain Apple Powerbooks. The 2.4 driver is also based on work by Jordan Crouse.
The driver currently leaves the flat panel as it was set up by the BIOS. In most cases this displays the same image on flat panel and VGA outputs. The goal for the driver is to support multi-head operation, and multiple 69030 chips. The driver supports operation without a VGA BIOS for embedded applications, but currently contains no flat panel setup code.
These are experimental Linux 2.2 and 2.4 framebuffer drivers for the Asiliant 69030 graphics chip. This chip was previously available from Intel, and is descended from a Chips and Technologies part. The 2.2 driver is thus based on the Linux chipsfb.c driver, which supports the 65555 part in certain Apple Powerbooks. The 2.4 driver is also based on work by Jordan Crouse.
This driver is experimental, but is intended as a basis to merge into the mainstream kernel. Though the driver should work on the 69000, I currently have no 69000 hardware to test it on. Reports of using a panel and CRT simultaneously on 69000 are very interesting.
Current PowerPC kernels have a number of flaws in their machine check handling. The first fault is that they raise a SIGSEGV exception if the machine check occurs during user mode code. Many causes of machine check are not directly related to the current process. For example, on some platforms a PCI parity error detected while a PCI bus master writes into memory will cause a machine check. On some platforms a parity error reading data from the L2 cache in order to write it out to memory will cause a machine check.
