logo       

2.6 patch for h3800: msg#00008

handhelds.linux.kernel

Subject: 2.6 patch for h3800

I made some effort on porting h3800 to 2.6 kernel:
- Initial boot and serial console: I just needed to fix some compilation
problems.
- ASIC2: I fixed problems related to devices registration, interrupt
handling and suspend/resume handling.
- asic2_adc: It was hanging during suspend while doing "down
(&adc->lock)", so I commented it. Also I added bus type to device driver
struct.
- asic2_key: The same as asic2_adc. Also I added the h3800 power button
handling here. May be it is not the suitable location.
- The sleeve: This took the most effort.

I added three drivers for:
- ASIC1: It now handles only backlight and LCD power.
- LEDs
- Battery: Currently it only enables charging and flashes charging led
when AC is connected.

I made a small change to ledscore.c so the battery driver can turn on
the charging LED.

So now the following is working:
- The sleeve and PCMCIA are working
- LCD and backlight control are working
- Touchscreen
- The buttons are working
- Suspend and resume are working. I don't know yet the power consumption
status when suspended.
- Charging should be partially working.

Currently I have the following problems:
- Xfbdev crashes after resume. Also it hangs apmd if apmd is running
during suspend.
- Xfbdev doesn't see the buttons events if started by init. I have to
restart Xfbdev manually from the serial console.

I know that the following is not working:
- Sound
- MMC
- USB
- IRDA
- Battery status
- May be others

Also I attached my .config file. Please note that I didn't enable jffs2
because my ipaq boots from a microdrive.

All my work was based on 2.4 code and the other ipaqs code in 2.6.

Attachment: h3800.diff
Description: Text Data

Attachment: h3800.config
Description: Text document

_______________________________________________
Kernel-discuss mailing list
Kernel-discuss-CN5wO63fgwogsBAKwltoeQ@xxxxxxxxxxxxxxxx
https://handhelds.org/mailman/listinfo/kernel-discuss
<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise