April 2006 - e3-hacking

Sound driver. Cliff help please :)
by Mark Underwood 10 Apr '06

10 Apr '06

Cliff, I'm trying to write a sound driver for the E3 under Linux-2.6 and would really appreciate any help you would be willing to offer. I can see by probing the board that the Voice Codec (VC) is sending 16 bits of data (from the mic) to the modem on timeslot0. The PCM clock is just over 2MHz which would give you 16 x 16bit timeslots. I'm assuming that data is sent from the modem to the VC (for the speaker) on timeslot0 as well, although I haven't confirmed that. I have looked for a datasheet on the VC but can only find a datasheet which gives a general overview of the 3 chips that makeup the modem, which doesn't tell me the PCM configuration for example. If you have such a datasheet for the VC could you please send it to me :) Also, if you wouldn't mind, could you send the setup of the McBSP to talk to the VC as I'm having trouble trying to work it out (without any schematics, etc). Cheers, Mark ___________________________________________________________ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com

1 0

[PATCH] add-RGB444-support-to-omapfb.patch
by Mark Underwood 07 Apr '06

07 Apr '06

This is an updated version of my patch that adds support for RGB444 mode for the internal LCD controller which now applies against linux-2.6.16 with the patch-2.6.16-omap2 applied. Jonathan McDowell posted a slightly modified version of my original patch to this list previously: http://Linux.omap.com/pipermail/linux-omap-open-source/2006-April/006839.ht… This patch is used by the Amstrad Delta (E3). Signed-Off-By: Mark Underwood <basicmark(a)yahoo.com> ___________________________________________________________ Win a BlackBerry device from O2 with Yahoo!. Enter now. http://www.yahoo.co.uk/blackberry

1 0

12bpp support in Linux-2.6.16
by Mark Underwood 06 Apr '06

06 Apr '06

Here is the 12bpp support updated for Linux-2.6.16. Mark ___________________________________________________________ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com

1 0

RE: [E3-hacking] External keyboard (mailboard) support for 2.6
by Cliff Lawson 05 Apr '06

05 Apr '06

> -----Original Message----- > From: Matt Callow [mailto:mc-lists@tesco.net] > > it's still useful to have. Whilst looking at the code, I noticed that > the qwe interrupt handler writes to latch2 > AMS_DELTA_HDW_OP_SCARD_2_MASK > (I'm assuming AMS_DELTA_HDW_OP_SCARD_2_MASK is 0x400), > setting it at the > start and clearing it at the end. Is this for debug purposes only? I > noticed a similar thing in the FIQ handler using GPIO6. Yup I *think* they are just being used to tickle "spare" pins to trigger an LA or a scope. I'm kind of surprised that hasn't been removed in fact though I'm not sure of the vintage of the tree I have on my machine (and yes it's 0x400) > I also notice that the driver has some code for writing to > the keyboard, > but data never seems to be sent. Is my understanding correct? > Does the > keyboard accept data? Well the use of it we make is because the PS/2 keyboard controller has been known to die (sometimes as often as about once every 5 minutes in fact) - it's a standard, masked part that we have no control over - so what we do is send it 0xEE commands and see if it echoes. If it does all is well, if it doesn't we switch the 5V line to it to reset the chip. But we don't transmit anything else to it as we're happy with the scanset and typematic rates it defaults to. Cliff This e-mail and any attachments are confidential and intended exclusively for the addressee. If you are not the intended recipient please delete it from your system and notify the sender immediately. This message is attributed to the sender and may not necessarily reflect the views of Amstrad Plc or its subsidiaries. For further information on Amstrad Plc please visit our website: www.amstrad.com Amstrad Plc. Brentwood House 169 Kings Road Brentwood Essex CM14 4EF Registered in England : No. 955321

1 0

FIQ
by Matt Callow 05 Apr '06

05 Apr '06

Hi, I've been trying to install the FIQ handler from the MontaVista 2.4 kernel. Currently without much success. When the first gpio interrupt occurs I get a data abort, as show below: <2>Bad mode in data abort handler detected: mode FIQ_32 Internal error: Oops - bad mode: 0 [#1] Modules linked in: at76c505_rfmd2958 at76c503 at76_usbdfu CPU: 0 PC is at 0xffff0028 LR is at serial8250_startup+0x384/0x488 pc : [<ffff0028>] lr : [<c016571c>] Not tainted sp : c1941d78 ip : 00000002 fp : c1941dec r10: c0309ecc r9 : 00000000 r8 : c0309c44 r7 : 60000013 r6 : 00000288 r5 : c030a2b4 r4 : 00000000 r3 : eb000000 r2 : 00000002 r1 : 00000005 r0 : c030a2b4 Flags: nZCv IRQs off FIQs off Mode FIQ_32 Segment user Control: 317F Table: 11B34000 DAC: 00000015 Process microcom (pid: 73, stack limit = 0xc1940194) Stack: (0xc1941d78 to 0xc1942000) 1d60: c030a2b4 00000005 1d80: 00000002 eb000000 00000000 c030a2b4 00000288 60000013 c0309c44 00000000 1da0: c0309ecc c1941dec 00000002 c1941d78 c016571c ffff0028 600000d1 ffffffff 1dc0: c0309ecc c030a2b4 c1b26d20 c1e76f08 00000000 00000000 c15fe2c0 00000002 1de0: c1941e10 c1941df0 c01612e8 c01653a8 00000000 c1e76f08 c1b30000 c02aa1e4 1e00: c1940000 c1941e6c c1941e14 c01632f0 c0161260 c003b4c4 c1941e6c c1941e28 1e20: c014b6c0 c014a784 00000000 00000000 c1e60fc4 c1b26f20 c1e60fb4 c1b26a20 1e40: c1941e6c 00000000 c15fe2c0 c02a688c 00000000 00400041 c15fe2c0 00000002 1e60: c1941e9c c1941e70 c014c8dc c0163074 c1b30000 00000001 00000000 c1e77e04 1e80: c1940000 c1925cc4 00000001 00000000 c1941ecc c1941ea0 c0084f08 c014c6c0 1ea0: 00000001 c15fe2c0 00000000 c1925cc4 c0084d34 00000001 c1a4daa8 c0372220 1ec0: c1941ef8 c1941ed0 c00798b0 c0084d44 c15fe2c0 c1941f14 00000003 00000005 1ee0: c0023e04 c1940000 c15b5000 c1941f10 c1941efc c0079a2c c007977c 00000000 1f00: 00000002 c1941f6c c1941f14 c0079a80 c0079a08 c1a4daa8 c0372220 00000000 1f20: 00000003 c03803c8 00000101 00000001 00000000 c1940000 c15b5000 c1941f6c 1f40: c1941f4c c0079c88 c003a300 00000003 00000000 c15fe2c0 00000002 00000000 1f60: c1941f94 c1941f70 c0079dcc c0079a50 00000002 be82af8a be82aed4 00000005 1f80: c0023e04 400721fc c1941fa4 c1941f98 c0079e68 c0079d98 00000000 c1941fa8 1fa0: c0023c80 c0079e68 00000002 be82af8a 000137f8 00000002 00000000 00000002 1fc0: 00000002 be82af8a be82aed4 00000002 0000893c 00000002 400721fc 00008dc0 1fe0: 4005f5ec be82ad20 00008f0c 4005f610 60000010 000137f8 00000000 00000000 Backtrace: [<c0165398>] (serial8250_startup+0x0/0x488) from [<c01612e8>] (uart_startup+0x98/0x1f0) [<c0161250>] (uart_startup+0x0/0x1f0) from [<c01632f0>] (uart_open+0x28c/0x624) r8 = C1940000 r7 = C02AA1E4 r6 = C1B30000 r5 = C1E76F08 r4 = 00000000 [<c0163064>] (uart_open+0x0/0x624) from [<c014c8dc>] (tty_open+0x22c/0x398) [<c014c6b0>] (tty_open+0x0/0x398) from [<c0084f08>] (chrdev_open+0x1d4/0x1f4) [<c0084d34>] (chrdev_open+0x0/0x1f4) from [<c00798b0>] (__dentry_open+0x144/0x28c) [<c007976c>] (__dentry_open+0x0/0x28c) from [<c0079a2c>] (nameidata_to_filp+0x34/0x48) [<c00799f8>] (nameidata_to_filp+0x0/0x48) from [<c0079a80>] (filp_open+0x40/0x48) r4 = 00000002 [<c0079a40>] (filp_open+0x0/0x48) from [<c0079dcc>] (do_sys_open+0x44/0xd0) r5 = 00000000 r4 = 00000002 [<c0079d88>] (do_sys_open+0x0/0xd0) from [<c0079e68>] (sys_open+0x10/0x14) [<c0079e58>] (sys_open+0x0/0x14) from [<c0023c80>] (ret_fast_syscall+0x0/0x2c) Code: ea000078 e3a0c4ff e38cc8fe e38ccccb (e59cb014) From what I can make of this, the FIQ handler is being executed (PC is at 0xffff0028), so if look at the FIQ code (which is at 0xffff001c), I see fff001c: e3a0c4ff mov r12, #-16777216 ; 0xff000000 fff0020: e38cc8fe orr r12, r12, #16646144 ; 0xfe0000 fff0024: e38ccccb orr r12, r12, #51968 ; 0xcb00 fff0028: e59cb014 ldr r11, [r12, #20] fff002c: e589b030 str r11, [r9, #48] fff0030: e3a0c4ff mov r12, #-16777216 ; 0xff000000 fff0034: e38cc73f orr r12, r12, #16515072 ; 0xfc0000 fff0038: e38cca0e orr r12, r12, #57344 ; 0xe000 fff003c: e599a044 ldr r10, [r9, #68] fff0040: e28aa001 add r10, r10, #1 ; 0x1 fff0044: e589a044 str r10, [r9, #68] So, at 0xfff0028, it's trying to load r11 with the contents of 0xfffecb14, which is the SIR_FIQ_CODE register. How can that be causing a data abort? Matt

1 0

RE: [E3-hacking] External keyboard (mailboard) support for 2.6
by Cliff Lawson 05 Apr '06

05 Apr '06

> -----Original Message----- > From: Matt Callow [mailto:mc-lists@tesco.net] > Sent: 04 April 2006 12:57 > To: Discussion of the Amstrad E3 emailer hardware/software > Subject: [E3-hacking] External keyboard (mailboard) support for 2.6 > > I've been working on this for a while now, but I still cant get it to > work reliably. It took us about a YEAR(!) to get the bloody keyboard working reliably so you're on the early stage of your journey. In a future design I'm going to stick in something like an 8 bit Atmel AVR to mop up IO and have the dedicated task of talking to these bloody clock master PS/2 controllers to save the aggro. (it is a shame that Linux makes you go through such hoops for fast interrupt service though and is the reason why I never use the term RTOS applied to Linux even if the kernel has "realtime" patches - I can't help thinking this would have been easier in VxWorks!) But anyway, after a couple of gentle nudges: www.ourcottage.plus.com/ams_keyb_mod.c (from kernel/drivers/char) I'm not sure what dependent .h you might need so holler when it won't build! Cliff This e-mail and any attachments are confidential and intended exclusively for the addressee. If you are not the intended recipient please delete it from your system and notify the sender immediately. This message is attributed to the sender and may not necessarily reflect the views of Amstrad Plc or its subsidiaries. For further information on Amstrad Plc please visit our website: www.amstrad.com Amstrad Plc. Brentwood House 169 Kings Road Brentwood Essex CM14 4EF Registered in England : No. 955321

2 1

GPE update
by David Given 04 Apr '06

04 Apr '06

Well, I have GPE up and running now. And the verdict is... oh, dear... The good news is that GPE will *just* start in 32MB of RAM. The bad news is that trying to actually do anything results in the system chugging badly, as Linux frantically discards text pages and reloads them over USB, and ultimately crashes. I tried giving it some swap, again over USB, and it didn't crash any more --- but it's awfully sluggish... you wouldn't want to use it in real life. The most expensive app was, as you might expect, Mozilla Minimo which idled at about 6MB. Embarrassingly, the Watch app, which draws an antialiased clock face on the screen, can only update the second hand about once every two seconds. The good news is that I suspect this was extensively stress testing the kernel, especially the USB subsystem, and it's all fine! (Although the screen colours are screwed up due to 444/545 mismatch.) I should give Opie a try to see if it's any better. Would anyone be interested in the kernel.conf and filesystem patch I used to get it running? -- +- David Given --McQ-+ "If you're up against someone more intelligent | dg(a)cowlark.com | than you are, do something insane and let him think | (dg(a)tao-group.com) | himself to death." --- Pyanfar Chanur +- www.cowlark.com --+

1 0

External keyboard (mailboard) support for 2.6
by Matt Callow 04 Apr '06

04 Apr '06

I've been working on this for a while now, but I still cant get it to work reliably. I have tried installing a interrupt handler and using code based on serio/parkbd.c. This tries to read 1 bit every interrupt and doesn't work very well.I've also tried polling the entire bitstream after the first interrupt, this works better, but still gives false data. If I press a key (e.g. space), I expect to get: 0x4b // scancode for space 0xf0 // key released 0x4b // scancode for space But I hardly every get the 2nd 0x4b, and I don't always get the first 2 bytes correctly either. I think this is because I am missing some bits due to the interrupt processing latency. Cliff Lawson said in an earlier post that the bit stream is clocked at about 70kHz and apparently the 5910 can only handle about 13k ints/second on linux. Cliff said that Amstrad used a FIQ handler to read the keyboard in the 2.4 kernel source. There does not seem to he a FIQ handler for omap in the 2.6 kernel but we do have most of the amstrad code available under GPL. (it's in arch/arm/kernel/fiq-qwerty.S and arch/arm/kernel/irq.c). As far as I can tell, this works as follows: * fiq handler is installed * gpio interrupt is changed to be a fiq * fiq handler is invoked when a gpio interrupt is raised (in the E3 this may be either modem of mailboard) * If it's a modem interrupt, pass is on (more of that later) * If it's a mailboard interrupt, process the next bit in the bitstream, once a full character is recived, pass it on The fiq handler passes requests to irq context by faking a 32kHz interrupt (this means that the 32kHz timer interrupt cannot be used for it's orginal purpose). The 32kHz interrupt handler then reads some shared memory to determine which gpio interrupt(s) occured and invokes the appropriate handler. The end result is that a modem interrupt generates one fiq and one irq, whilst a mailboard interrupt generates one fiq for every bit in the keyboard data but an irq is only generated when a character has been recieved. There is also some code (in irq.c) to check if the fiq handler is stuck, and inject a gpio interrupt if it is. So, I'm begining to think that I'll need to re-implement most of this to get the mailboard to work. What do other people think? It looks like it's going to be a fair bit of work, but, I don't really see any other way of sucessfully capturing the serial keyboard data. Matt

1 0

[PATCH 1/3] Add backlight support for Amstrad Delta
by Jonathan McDowell 04 Apr '06

04 Apr '06

This patch adds support for the Amstrad Delta LCD backlight. It's the first patch in a series of 3 enabling full LCD support for the Delta and is the least intrusive, allowing control of the backlight through the existing backlight class infrastructure. Signed-Off-By: Jonathan McDowell <noodles(a)earth.li> diff --git a/arch/arm/configs/ams_delta_defconfig b/arch/arm/configs/ams_delta_defconfig index 03f02dd..7cc0727 100644 --- a/arch/arm/configs/ams_delta_defconfig +++ b/arch/arm/configs/ams_delta_defconfig @@ -1,7 +1,7 @@ # # Automatically generated make config: don't edit # Linux kernel version: 2.6.16-omap1 -# Wed Mar 22 10:53:48 2006 +# Sun Apr 2 16:00:11 2006 # CONFIG_ARM=y CONFIG_MMU=y @@ -623,13 +623,44 @@ CONFIG_I2C_OMAP=y # # Graphics support # -# CONFIG_FB is not set +CONFIG_FB=y +# CONFIG_FB_CFB_FILLRECT is not set +# CONFIG_FB_CFB_COPYAREA is not set +# CONFIG_FB_CFB_IMAGEBLIT is not set +# CONFIG_FB_MACMODES is not set +# CONFIG_FB_MODE_HELPERS is not set +# CONFIG_FB_TILEBLITTING is not set +# CONFIG_FB_S1D13XXX is not set +CONFIG_FB_OMAP=y +# CONFIG_FB_OMAP_LCDC_EXTERNAL is not set +# CONFIG_FB_OMAP_LCD_LPH8923 is not set +# CONFIG_FB_OMAP_BOOTLOADER_INIT is not set +# CONFIG_FB_OMAP_DMA_TUNE is not set +# CONFIG_FB_VIRTUAL is not set # # Console display driver support # # CONFIG_VGA_CONSOLE is not set CONFIG_DUMMY_CONSOLE=y +CONFIG_FRAMEBUFFER_CONSOLE=y +# CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set +# CONFIG_FONTS is not set +CONFIG_FONT_8x8=y +CONFIG_FONT_8x16=y + +# +# Logo configuration +# +CONFIG_LOGO=y +# CONFIG_LOGO_LINUX_MONO is not set +# CONFIG_LOGO_LINUX_VGA16 is not set +CONFIG_LOGO_LINUX_CLUT224=y +CONFIG_BACKLIGHT_LCD_SUPPORT=y +CONFIG_BACKLIGHT_CLASS_DEVICE=y +CONFIG_BACKLIGHT_DEVICE=y +# CONFIG_LCD_CLASS_DEVICE is not set +CONFIG_BACKLIGHT_AMS_DELTA=y # # Sound diff --git a/arch/arm/mach-omap1/board-ams-delta.c b/arch/arm/mach-omap1/board-ams-delta.c index 6178f04..7475587 100644 --- a/arch/arm/mach-omap1/board-ams-delta.c +++ b/arch/arm/mach-omap1/board-ams-delta.c @@ -84,6 +84,15 @@ static struct omap_board_config_kernel a { OMAP_TAG_UART, &ams_delta_uart_config }, }; +static struct platform_device ams_delta_bl_device = { + .name = "ams-delta-bl", + .id = -1, +}; + +static struct platform_device *ams_delta_devices[] __initdata = { + &ams_delta_bl_device, +}; + static void __init ams_delta_init(void) { iotable_init(ams_delta_io_desc, ARRAY_SIZE(ams_delta_io_desc)); @@ -94,6 +103,8 @@ static void __init ams_delta_init(void) /* Clear latch2 (NAND, LCD, modem enable) */ ams_delta_latch2_write(~0, 0); + + platform_add_devices(ams_delta_devices, ARRAY_SIZE(ams_delta_devices)); } static void __init ams_delta_map_io(void) diff --git a/drivers/video/backlight/Kconfig b/drivers/video/backlight/Kconfig index 9d996f2..5f02b00 100644 --- a/drivers/video/backlight/Kconfig +++ b/drivers/video/backlight/Kconfig @@ -42,6 +42,14 @@ config LCD_DEVICE depends on LCD_CLASS_DEVICE default y +config BACKLIGHT_AMS_DELTA + tristate "Amstrad Delta (E3) backlight driver" + depends on BACKLIGHT_DEVICE && MACH_AMS_DELTA + default y + help + If you have an Amstrad Delta (E3) videophone, say y to enable + the backlight driver. + config BACKLIGHT_CORGI tristate "Sharp Corgi Backlight Driver (SL-C7xx Series)" depends on BACKLIGHT_DEVICE && PXA_SHARPSL diff --git a/drivers/video/backlight/Makefile b/drivers/video/backlight/Makefile index 744210c..2a793ea 100644 --- a/drivers/video/backlight/Makefile +++ b/drivers/video/backlight/Makefile @@ -1,6 +1,7 @@ # Backlight & LCD drivers obj-$(CONFIG_LCD_CLASS_DEVICE) += lcd.o +obj-$(CONFIG_BACKLIGHT_AMS_DELTA) += ams_delta_bl.o obj-$(CONFIG_BACKLIGHT_CLASS_DEVICE) += backlight.o obj-$(CONFIG_BACKLIGHT_CORGI) += corgi_bl.o obj-$(CONFIG_BACKLIGHT_HP680) += hp680_bl.o diff --git a/drivers/video/backlight/ams_delta_bl.c b/drivers/video/backlight/ams_delta_bl.c new file mode 100644 index 0000000..6b84744 --- /dev/null +++ b/drivers/video/backlight/ams_delta_bl.c @@ -0,0 +1,172 @@ +/* + * Backlight driver for Amstrad E3 (Delta) videophone. + * + * Copyright (C) 2006 Jonathan McDowell <noodles(a)earth.li> + * + * Based on Richard Purdie's Corgi driver. + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License version 2 as + * published by the Free Software Foundation. + * + */ + +#include <linux/module.h> +#include <linux/kernel.h> +#include <linux/init.h> +#include <linux/fb.h> +#include <linux/backlight.h> +#include <linux/platform_device.h> + +#include <asm/arch/omap16xx.h> +#include <asm/arch/board-ams-delta.h> + +#define AMS_DELTA_DEFAULT_INTENSITY 112 +#define AMS_DELTA_MAX_INTENSITY 255 + +static int ams_delta_bl_powermode = FB_BLANK_UNBLANK; +static int current_intensity = 0; + +static void ams_delta_bl_send_intensity(int intensity) +{ + if (ams_delta_bl_powermode != FB_BLANK_UNBLANK) { + intensity = 0; + } + + omap_writeb(intensity, OMAP16XX_PWL_ENABLE); +} + +static void ams_delta_bl_blank(int blank) +{ + switch(blank) { + + case FB_BLANK_NORMAL: + case FB_BLANK_VSYNC_SUSPEND: + case FB_BLANK_HSYNC_SUSPEND: + case FB_BLANK_POWERDOWN: + if (ams_delta_bl_powermode == FB_BLANK_UNBLANK) { + ams_delta_latch2_write(AMS_DELTA_LATCH2_LCD_VBLEN, 0); + ams_delta_bl_send_intensity(0); + ams_delta_bl_powermode = blank; + } + break; + case FB_BLANK_UNBLANK: + if (ams_delta_bl_powermode != FB_BLANK_UNBLANK) { + ams_delta_latch2_write(AMS_DELTA_LATCH2_LCD_VBLEN, + AMS_DELTA_LATCH2_LCD_VBLEN); + ams_delta_bl_powermode = blank; + ams_delta_bl_send_intensity(current_intensity); + } + break; + } +} + +#ifdef CONFIG_PM +static int ams_delta_bl_suspend(struct platform_device *dev, pm_message_t state) +{ + ams_delta_bl_blank(FB_BLANK_POWERDOWN); + return 0; +} + +static int ams_delta_bl_resume(struct platform_device *dev) +{ + ams_delta_bl_blank(FB_BLANK_UNBLANK); + return 0; +} +#else +#define ams_delta_bl_suspend NULL +#define ams_delta_bl_resume NULL +#endif + + +static int ams_delta_bl_set_power(struct backlight_device *bd, int state) +{ + ams_delta_bl_blank(state); + return 0; +} + +static int ams_delta_bl_get_power(struct backlight_device *bd) +{ + return ams_delta_bl_powermode; +} + +static int ams_delta_bl_set_intensity(struct backlight_device *bd, + int intensity) +{ + if (intensity > AMS_DELTA_MAX_INTENSITY) + intensity = AMS_DELTA_MAX_INTENSITY; + ams_delta_bl_send_intensity(intensity); + current_intensity = intensity; + return 0; +} + +static int ams_delta_bl_get_intensity(struct backlight_device *bd) +{ + return current_intensity; +} + +static struct backlight_properties ams_delta_bl_data = { + .owner = THIS_MODULE, + .get_power = ams_delta_bl_get_power, + .set_power = ams_delta_bl_set_power, + .max_brightness = AMS_DELTA_MAX_INTENSITY, + .get_brightness = ams_delta_bl_get_intensity, + .set_brightness = ams_delta_bl_set_intensity, +}; + +static struct backlight_device *ams_delta_backlight_device; + +static int __init ams_delta_bl_probe(struct platform_device *pdev) +{ + ams_delta_backlight_device = backlight_device_register("ams-delta-bl", + NULL, &ams_delta_bl_data); + if (IS_ERR(ams_delta_backlight_device)) + return PTR_ERR(ams_delta_backlight_device); + + omap_writeb(1, OMAP16XX_PWL_CLK_ENABLE); + ams_delta_latch2_write(AMS_DELTA_LATCH2_LCD_VBLEN, + AMS_DELTA_LATCH2_LCD_VBLEN); + ams_delta_bl_set_intensity(NULL, AMS_DELTA_DEFAULT_INTENSITY); + + printk("Amstrad Delta backlight driver initialized.\n"); + return 0; +} + +static int ams_delta_bl_remove(struct platform_device *dev) +{ + backlight_device_unregister(ams_delta_backlight_device); + + ams_delta_bl_set_intensity(NULL, 0); + omap_writeb(0, OMAP16XX_PWL_CLK_ENABLE); + ams_delta_latch2_write(AMS_DELTA_LATCH2_LCD_VBLEN, 0); + + printk("Amstrad Delta backlight driver unloaded\n"); + return 0; +} + +static struct platform_driver ams_delta_bl_driver = { + .probe = ams_delta_bl_probe, + .remove = ams_delta_bl_remove, + .suspend = ams_delta_bl_suspend, + .resume = ams_delta_bl_resume, + .driver = { + .name = "ams-delta-bl", + }, +}; + +static int __init ams_delta_bl_init(void) +{ + return platform_driver_register(&ams_delta_bl_driver); +} + +static void __exit ams_delta_bl_exit(void) +{ + platform_driver_unregister(&ams_delta_bl_driver); +} + +module_init(ams_delta_bl_init); +module_exit(ams_delta_bl_exit); + +MODULE_AUTHOR("Jonathan McDowell <noodles(a)earth.li>"); +MODULE_DESCRIPTION("Amstrad Delta backlight driver"); +MODULE_LICENSE("GPLv2");

4 5

RE: [E3-hacking] keypad layout
by Cliff Lawson 03 Apr '06

03 Apr '06

Shades of reinventing the wheel here - I already did the Linux keyboard layouts with sensible key code returns to Linux (IMHO). I'm about to bugger off home for the weekend but if someone gives me a nudge on Monday you're welcome the to files I have already (I spent AGES trying to come up with the best layout and it'd be a shame to see this go to waste!) By the way, if you want a good belly laugh, I'd highly recommend folks watch Jonathan Ross at 10:35pm, BBC1 tonight for an interview with Alan about The Apprentice and a quite "interesting" piece of Atmel AVR ATMega16 based electronics I threw together! Cliff > -----Original Message----- > From: Jonathan McDowell [mailto:noodles@earth.li] > Subject: Re: [E3-hacking] keypad layout This e-mail and any attachments are confidential and intended exclusively for the addressee. If you are not the intended recipient please delete it from your system and notify the sender immediately. This message is attributed to the sender and may not necessarily reflect the views of Amstrad Plc or its subsidiaries. For further information on Amstrad Plc please visit our website: www.amstrad.com Amstrad Plc. Brentwood House 169 Kings Road Brentwood Essex CM14 4EF Registered in England : No. 955321

8 7