(matrix_keypad driver) Re: qi_lb60_keypad driver question?

(matrix_keypad driver) Re: qi_lb60_keypad driver question?

[Xiangfu Liu]

[-- Attachment #1: Type: text/plain, Size: 557 bytes --]

Hi
now the keypad in Ben NanoNote[1] is work.
problem is I don't know how to write the special assemble key of matrix_key driver. some kind of 'SHIFT', like the red key in [2].
when I press the 'RED UP POINT' + 'W' = '@'

attach is the Ben keypad driver platform.c:260 ~ 364 lines.

thanks for any advice  

[1] http://www.qi-hardware.com/products/ben-nanonote/
[2] http://downloads.qi-hardware.com/hardware/mechanical/ben/2009_08_26/keyboard_problem_2.JPG

-- 
Best Regards
Xiangfu Liu
Email: xiangfu at qi-hardware dot com
Web: http://www.qi-hardware.com

[-- Attachment #2: platform.c --]
[-- Type: text/x-csrc, Size: 10464 bytes --]

/*
 * Platform device support for Jz4740 SoC.
 *
 * Copyright 2007, <yliu@ingenic.cn>
 *
 * This file is licensed under the terms of the GNU General Public
 * License version 2.  This program is licensed "as is" without any
 * warranty of any kind, whether express or implied.
 */

#include <linux/device.h>
#include <linux/platform_device.h>
#include <linux/kernel.h>
#include <linux/init.h>
#include <linux/resource.h>
#include <linux/mtd/jz4740_nand.h>
#include <linux/jz4740_fb.h>
#include <linux/input/matrix_keypad.h>
#include <linux/mtd/jz4740_nand.h>

#include <asm/jzsoc.h>

/* OHCI (USB full speed host controller) */
static struct resource jz_usb_ohci_resources[] = {
	[0] = {
		.start		= CPHYSADDR(UHC_BASE), // phys addr for ioremap
		.end		= CPHYSADDR(UHC_BASE) + 0x10000 - 1,
		.flags		= IORESOURCE_MEM,
	},
	[1] = {
		.start		= IRQ_UHC,
		.end		= IRQ_UHC,
		.flags		= IORESOURCE_IRQ,
	},
};

/* The dmamask must be set for OHCI to work */
static u64 ohci_dmamask = ~(u32)0;

static struct platform_device jz_usb_ohci_device = {
	.name		= "jz-ohci",
	.id		= 0,
	.dev = {
		.dma_mask		= &ohci_dmamask,
		.coherent_dma_mask	= 0xffffffff,
	},
	.num_resources	= ARRAY_SIZE(jz_usb_ohci_resources),
	.resource	= jz_usb_ohci_resources,
};

/*** LCD controller ***/
static struct resource jz_lcd_resources[] = {
	[0] = {
		.start          = CPHYSADDR(LCD_BASE),
		.end            = CPHYSADDR(LCD_BASE) + 0x10000 - 1,
		.flags          = IORESOURCE_MEM,
	},
	[1] = {
		.start          = IRQ_LCD,
		.end            = IRQ_LCD,
		.flags          = IORESOURCE_IRQ,
	}
};

static u64 jz_lcd_dmamask = ~(u32)0;

static struct platform_device jz_lcd_device = {
	.name           = "jz-lcd",
	.id             = 0,
	.dev = {
		.dma_mask               = &jz_lcd_dmamask,
		.coherent_dma_mask      = 0xffffffff,
	},
	.num_resources  = ARRAY_SIZE(jz_lcd_resources),
	.resource       = jz_lcd_resources,
};

/* UDC (USB gadget controller) */
static struct resource jz_usb_gdt_resources[] = {
	[0] = {
		.start		= CPHYSADDR(UDC_BASE),
		.end		= CPHYSADDR(UDC_BASE) + 0x10000 - 1,
		.flags		= IORESOURCE_MEM,
	},
	[1] = {
		.start		= IRQ_UDC,
		.end		= IRQ_UDC,
		.flags		= IORESOURCE_IRQ,
	},
};

static u64 udc_dmamask = ~(u32)0;

static struct platform_device jz_usb_gdt_device = {
	.name		= "jz-udc",
	.id		= 0,
	.dev = {
		.dma_mask		= &udc_dmamask,
		.coherent_dma_mask	= 0xffffffff,
	},
	.num_resources	= ARRAY_SIZE(jz_usb_gdt_resources),
	.resource	= jz_usb_gdt_resources,
};

/** MMC/SD controller **/
static struct resource jz_mmc_resources[] = {
	[0] = {
		.start          = CPHYSADDR(MSC_BASE),
		.end            = CPHYSADDR(MSC_BASE) + 0x10000 - 1,
		.flags          = IORESOURCE_MEM,
	},
	[1] = {
		.start          = IRQ_MSC,
		.end            = IRQ_MSC,
		.flags          = IORESOURCE_IRQ,
	}
};

static u64 jz_mmc_dmamask =  ~(u32)0;

static struct platform_device jz_mmc_device = {
	.name = "jz-mmc",
	.id = 0,
	.dev = {
		.dma_mask               = &jz_mmc_dmamask,
		.coherent_dma_mask      = 0xffffffff,
	},
	.num_resources  = ARRAY_SIZE(jz_mmc_resources),
	.resource       = jz_mmc_resources,
};

/** I2C controller **/
static struct resource jz_i2c_resources[] = {
	[0] = {
		.start          = CPHYSADDR(I2C_BASE),
		.end            = CPHYSADDR(I2C_BASE) + 0x10000 - 1,
		.flags          = IORESOURCE_MEM,
	},
	[1] = {
		.start          = IRQ_I2C,
		.end            = IRQ_I2C,
		.flags          = IORESOURCE_IRQ,
	}
};

static u64 jz_i2c_dmamask =  ~(u32)0;

static struct platform_device jz_i2c_device = {
	.name = "jz_i2c",
	.id = 0,
	.dev = {
		.dma_mask               = &jz_i2c_dmamask,
		.coherent_dma_mask      = 0xffffffff,
	},
	.num_resources  = ARRAY_SIZE(jz_i2c_resources),
	.resource       = jz_i2c_resources,
};

static struct resource jz_nand_resources[] = {
	[0] = {
		.start          = CPHYSADDR(EMC_BASE),
		.end            = CPHYSADDR(EMC_BASE) + 0x10000 - 1,
		.flags          = IORESOURCE_MEM,
	},
};

#ifdef QI_LB60_2GB_NAND
static struct nand_ecclayout qi_lb60_ecclayout = {
	.eccbytes = 72,
        .eccpos = {
                12, 13, 14, 15, 16, 17, 18, 19,
		20, 21, 22, 23, 24, 25, 26, 27, 
		28, 29, 30, 31, 32, 33, 34, 35,
		36, 37, 38, 39, 40, 41, 42, 43,
		44, 45, 46, 47, 48, 49, 50, 51, 
		52, 53, 54, 55, 56, 57, 58, 59, 
		60, 61, 62, 63, 64, 65, 66, 67, 
		68, 69, 70, 71, 72, 73, 74, 75, 
		76, 77, 78, 79, 80, 81, 82, 83},
        .oobfree = {
 		{.offset = 2,
		 .length = 10},
		{.offset = 84,
		 .length = 44}}
};
 
static struct mtd_partition qi_lb60_partitions[] = {
	{ .name = "NAND BOOT partition",
	  .offset = 0 * 0x100000,
	  .size = 4 * 0x100000,
 	},
	{ .name = "NAND KERNEL partition",
	  .offset = 4 * 0x100000,
	  .size = 4 * 0x100000,
 	},
	{ .name = "NAND ROOTFS partition",
	  .offset = 8 * 0x100000,
	  .size = 504 * 0x100000,
 	},
	{ .name = "NAND DATA partition",
	  .offset = 512 * 0x100000,
	  .size = (512 + 1024) * 0x100000,
 	},
};
#else
static struct nand_ecclayout qi_lb60_ecclayout = {
	.eccbytes = 36,
	.eccpos = {
		6,  7,  8,  9,  10, 11, 12, 13,
		14, 15, 16, 17, 18, 19, 20, 21,
		22, 23, 24, 25, 26, 27, 28, 29,
		30, 31, 32, 33, 34, 35, 36, 37,
		38, 39, 40, 41},
	.oobfree = {
		{.offset = 2,
		 .length = 4},
		{.offset = 42,
		 .length = 22}}
};

static struct mtd_partition qi_lb60_partitions[] = {
	{ .name = "NAND BOOT partition",
	  .offset = 0 * 0x100000,
	  .size = 4 * 0x100000,
 	},
	{ .name = "NAND KERNEL partition",
	  .offset = 4 * 0x100000,
	  .size = 4 * 0x100000,
 	},
	{ .name = "NAND ROOTFS partition",
	  .offset = 8 * 0x100000,
	  .size = 504 * 0x100000,
 	},
	{ .name = "NAND DATA partition",
	  .offset = 512 * 0x100000,
	  .size = 512 * 0x100000,
 	},
};
#endif /* QI_LB60_2GB_NAND */

static struct jz_nand_platform_data jz_nand_platform_data = {
	.num_partitions = ARRAY_SIZE(qi_lb60_partitions),
	.partitions = qi_lb60_partitions,
	.ecc_layout = &qi_lb60_ecclayout,
	.busy_gpio = 94,
};

static struct platform_device jz_nand_device = {
	.name = "jz4740-nand",
	.num_resources = ARRAY_SIZE(jz_nand_resources),
	.resource = jz_nand_resources,
	.dev = {
		.platform_data = &jz_nand_platform_data,
	}
};
/* #define KEEP_UART_ALIVE
 * don't define this. the keyboard and keyboard both work
 */

#define KEY_QI_QI	KEY_MINUS
#define KEY_QI_UPRED	KEY_F14
#define KEY_QI_VOLUP	KEY_VOLUMEDOWN
#define KEY_QI_VOLDOWN	KEY_VOLUMEUP

static const uint32_t qi_lb60_keymap[] = {
	KEY(0, 0, KEY_F1),	/* S2 */
	KEY(0, 1, KEY_F2),	/* S3 */
	KEY(0, 2, KEY_F3),	/* S4 */
	KEY(0, 3, KEY_F4),	/* S5 */
	KEY(0, 4, KEY_F5),	/* S6 */
	KEY(0, 5, KEY_F6),	/* S7 */
	KEY(0, 6, KEY_F7),	/* S8 */

	KEY(1, 0, KEY_Q),	/* S10 */
	KEY(1, 1, KEY_W),	/* S11 */
	KEY(1, 2, KEY_E),	/* S12 */
	KEY(1, 3, KEY_R),	/* S13 */
	KEY(1, 4, KEY_T),	/* S14 */
	KEY(1, 5, KEY_Y),	/* S15 */
	KEY(1, 6, KEY_U),	/* S16 */
	KEY(1, 7, KEY_I),	/* S17 */
	KEY(2, 0, KEY_A),	/* S18 */
	KEY(2, 1, KEY_S),	/* S19 */
	KEY(2, 2, KEY_D),	/* S20 */
	KEY(2, 3, KEY_F),	/* S21 */
	KEY(2, 4, KEY_G),	/* S22 */
	KEY(2, 5, KEY_H),	/* S23 */
	KEY(2, 6, KEY_J),	/* S24 */
	KEY(2, 7, KEY_K),	/* S25 */
	KEY(3, 0, KEY_ESC),	/* S26 */
	KEY(3, 1, KEY_Z),	/* S27 */
	KEY(3, 2, KEY_X),	/* S28 */
	KEY(3, 3, KEY_C),	/* S29 */
	KEY(3, 4, KEY_V),	/* S30 */
	KEY(3, 5, KEY_B),	/* S31 */
	KEY(3, 6, KEY_N),	/* S32 */
	KEY(3, 7, KEY_M),	/* S33 */
	KEY(4, 0, KEY_TAB),	/* S34 */
	KEY(4, 1, KEY_CAPSLOCK),	/* S35 */
	KEY(4, 2, KEY_BACKSLASH),	/* S36 */
	KEY(4, 3, KEY_APOSTROPHE),	/* S37 */
	KEY(4, 4, KEY_COMMA),	/* S38 */
	KEY(4, 5, KEY_DOT),	/* S39 */
	KEY(4, 6, KEY_SLASH),	/* S40 */
	KEY(4, 7, KEY_UP),	/* S41 */
	KEY(5, 0, KEY_O),	/* S42 */
	KEY(5, 1, KEY_L),	/* S43 */
	KEY(5, 2, KEY_EQUAL),	/* S44 */
	KEY(5, 3, KEY_QI_UPRED),	/* S45 */
	KEY(5, 4, KEY_SPACE),	/* S46 */
	KEY(5, 5, KEY_QI_QI),	/* S47 */
	KEY(5, 6, KEY_LEFTCTRL),	/* S48 */
	KEY(5, 7, KEY_LEFT),	/* S49 */
	KEY(6, 0, KEY_F8),	/* S50 */
	KEY(6, 1, KEY_P),	/* S51 */
	KEY(6, 2, KEY_BACKSPACE),/* S52 */
	KEY(6, 3, KEY_ENTER),	/* S53 */
	KEY(6, 4, KEY_QI_VOLUP),	/* S54 */
	KEY(6, 5, KEY_QI_VOLDOWN),	/* S55 */
	KEY(6, 6, KEY_DOWN),	/* S56 */
	KEY(6, 7, KEY_RIGHT),	/* S57 */

#ifndef KEEP_UART_ALIVE
	KEY(7, 0, KEY_LEFTSHIFT),	/* S58 */
	KEY(7, 1, KEY_LEFTALT),	/* S59 */
	KEY(7, 2, KEY_FN),	/* S60 */
#endif
};

static const struct matrix_keymap_data qi_lb60_keymap_data = {
	.keymap		= qi_lb60_keymap,
	.keymap_size	= ARRAY_SIZE(qi_lb60_keymap),
};

static const unsigned int qi_lb60_keypad_cols[] = {
	74, 75, 76, 77, 78, 79, 80, 81,
};

static const unsigned int qi_lb60_keypad_rows[] = {
	114, 115, 116, 117, 118, 119, 120,
#ifndef KEEP_UART_ALIVE
	122,
#endif
};

static struct matrix_keypad_platform_data qi_lb60_pdata = {
	.keymap_data = &qi_lb60_keymap_data,
	.col_gpios	= qi_lb60_keypad_cols,
	.row_gpios	= qi_lb60_keypad_rows,
	.num_col_gpios	= ARRAY_SIZE(qi_lb60_keypad_cols),
	.num_row_gpios	= ARRAY_SIZE(qi_lb60_keypad_rows),
	.col_scan_delay_us	= 10,
	.debounce_ms		= 10,
	.wakeup			= 1,
	.active_low		= 1,
};

static struct platform_device qi_lb60_keypad = {
	.name		= "matrix-keypad",
	.id		= -1,
	.dev		= {
		.platform_data = &qi_lb60_pdata,
	},
};

static struct fb_videomode qi_lb60_video_modes[] = {
	{
		.name = "320x240",
		.xres = 320,
		.yres = 240,
		.pixclock = 700000,
		.left_margin = 140,
		.right_margin = 273,
		.upper_margin = 20,
		.lower_margin = 1,
		.hsync_len = 1,
		.vsync_len = 1,
		.sync = 0,
		.vmode = FB_VMODE_NONINTERLACED,
	},
};

static struct jz4740_fb_platform_data qi_lb60_fb_data = {
	.width = 60,
	.height = 45,
	.num_modes = ARRAY_SIZE(qi_lb60_video_modes),
	.modes = qi_lb60_video_modes,
	.bpp = 24,
	.lcd_type = JZ_LCD_TYPE_8BIT_SERIAL,
};

static struct resource fb_resources[] = {
	[0] = {
		.start          = CPHYSADDR(LCD_BASE),
		.end            = CPHYSADDR(LCD_BASE) + 0x10000 - 1,
		.flags          = IORESOURCE_MEM,
	},
};

static struct platform_device qi_lb60_fb = {
	.name = "jz4740-fb",
	.id = -1,
	.num_resources = ARRAY_SIZE(fb_resources),
	.resource = fb_resources,
	.dev = {
		.dma_mask               = &jz_lcd_dmamask,
		.coherent_dma_mask      = 0xffffffff,
		.platform_data = &qi_lb60_fb_data,
	},
};

/* All */
static struct platform_device *jz_platform_devices[] __initdata = {
	&jz_usb_ohci_device,
	&jz_lcd_device,
	&jz_usb_gdt_device,
	&jz_mmc_device,
	&jz_nand_device,
	&jz_i2c_device,
	&qi_lb60_keypad,
	&qi_lb60_fb,
};

static int __init jz_platform_init(void)
{
	return platform_add_devices(jz_platform_devices, ARRAY_SIZE(jz_platform_devices));
}

arch_initcall(jz_platform_init);

Re: (matrix_keypad driver) Re: qi_lb60_keypad driver question?

[Dmitry Torokhov]

Hi,

On Mon, Aug 31, 2009 at 12:06:42AM +0800, Xiangfu Liu wrote:
> Hi
> now the keypad in Ben NanoNote[1] is work.  problem is I don't know
> how to write the special assemble key of matrix_key driver. some kind
> of 'SHIFT', like the red key in [2].  when I press the 'RED UP POINT'
> + 'W' = '@'
> 

Historically our KEY_* definitions did not include defines for symbols
like '@' because they do not have a dedicated key but rather being
produced as a combination of a primary key + modifier; the mapping is
done either in console driver or in X.

Looking at the picture of the device that you provided it appears that
your device does not have a dedicated '@' key so it should work in the
same fashion as above.

-- 
Dmitry

Re: (matrix_keypad driver) Re: qi_lb60_keypad driver question?

[Xiangfu Liu]

Hi Dmitry
sorry for the late reply. 
thanks for the info.
I will try to work on the console driver since our device don't have X.

will send report when I have any progress. 

Best Regards
Xiangfu




Dmitry Torokhov wrote:
> Hi,
> 
> On Mon, Aug 31, 2009 at 12:06:42AM +0800, Xiangfu Liu wrote:
>> Hi
>> now the keypad in Ben NanoNote[1] is work.  problem is I don't know
>> how to write the special assemble key of matrix_key driver. some kind
>> of 'SHIFT', like the red key in [2].  when I press the 'RED UP POINT'
>> + 'W' = '@'
>>
> 
> Historically our KEY_* definitions did not include defines for symbols
> like '@' because they do not have a dedicated key but rather being
> produced as a combination of a primary key + modifier; the mapping is
> done either in console driver or in X.
> 
> Looking at the picture of the device that you provided it appears that
> your device does not have a dedicated '@' key so it should work in the
> same fashion as above.
> 


-- 
Xiangfu Liu
Email: xiangfu at qi-hardware dot com
Web: http://www.qi-hardware.com

Re: (matrix_keypad driver) Re: qi_lb60_keypad driver question?

[Xiangfu Liu]

Hi Dmitry
Dmitry Torokhov wrote:
> Hi,
> Historically our KEY_* definitions did not include defines for symbols
> like '@' because they do not have a dedicated key but rather being
> produced as a combination of a primary key + modifier; the mapping is
> done either in console driver or in X.
> 
> Looking at the picture of the device that you provided it appears that
> your device does not have a dedicated '@' key so it should work in the
> same fashion as above.
> 

since we don't have X now. I google about this. I don't know how to 
modify the console driver. can you tell me which file I need look 
into? thanks.

I found an another method. we use busybox in rootfs. the busybox have 
command [dumpkmap] [loadkmap] [showkey],

-----------
in host system run :
/usr/bin/dumpkeys > normal_keymap
/usr/bin/loadkeys funky_mini_keyboard_keymap
/usr/bin/busybox dumpkmap > funky_mini_keyboard_keymap.bin
/usr/bin/loadkeys normal_keymap

then in target system run
"loadkmap funky_mini_keyboard_keymap.bin"
-----------

in our device have a two special keys
[RED UP POINT] keycode is 94
[QI] keycode is 93

the loadkeys alwasy like:
compose '|' 's' to '$' 

how to write the keycode to the loadkeys file.

I just found this method yesterday. not test yet.
anyone have experience on this?

thanks for advice

--
Best Regards
Xiangfu Liu
Email: xiangfu at qi-hardware dot com
Web: http://www.qi-hardware.com

Re: matrix_keypad driver, Combination keys

[Xiangfu Liu]

Xiangfu Liu wrote:
> Hi Dmitry
> Dmitry Torokhov wrote:
>> Hi,
>> Historically our KEY_* definitions did not include defines for symbols
>> like '@' because they do not have a dedicated key but rather being
>> produced as a combination of a primary key + modifier; the mapping is
>> done either in console driver or in X.
>>
>> Looking at the picture of the device that you provided it appears that
>> your device does not have a dedicated '@' key so it should work in the
>> same fashion as above.
>>
> 
> since we don't have X now. I google about this. I don't know how to 
> modify the console driver. can you tell me which file I need look 
> into? thanks.
> 
> I found an another method. we use busybox in rootfs. the busybox have 
> command [dumpkmap] [loadkmap] [showkey],
> 
> -----------
> in host system run :
> /usr/bin/dumpkeys > normal_keymap
> /usr/bin/loadkeys funky_mini_keyboard_keymap
> /usr/bin/busybox dumpkmap > funky_mini_keyboard_keymap.bin
> /usr/bin/loadkeys normal_keymap
> 
> then in target system run
> "loadkmap funky_mini_keyboard_keymap.bin"
> -----------
> 
> in our device have a two special keys
> [RED UP POINT] keycode is 94
> [QI] keycode is 93
> 

can I modify this function matrix_keyboard.c:103
static void matrix_keypad_scan(struct work_struct *work)
to detect the combination keys?
like:
1. if press the compose keys [RED UP POINT] just record
2. if next press the 'w'. will report '@' to OS.

if it's possible. how to report '@' to OS. 
I saw the source code is always report the keycode.

thanks for help
-- 
Xiangfu Liu
Email: xiangfu at qi-hardware dot com
Web: http://www.qi-hardware.com

Re: (matrix_keypad driver) Re: qi_lb60_keypad driver question?

[Xiangfu Liu]

Dmitry Torokhov wrote:
> Hi,
> 
> On Mon, Aug 31, 2009 at 12:06:42AM +0800, Xiangfu Liu wrote:
>> Hi
>> now the keypad in Ben NanoNote[1] is work.  problem is I don't know
>> how to write the special assemble key of matrix_key driver. some kind
>> of 'SHIFT', like the red key in [2].  when I press the 'RED UP POINT'
>> + 'W' = '@'
>>
> 
> Historically our KEY_* definitions did not include defines for symbols
> like '@' because they do not have a dedicated key but rather being
> produced as a combination of a primary key + modifier; the mapping is
> done either in console driver or in X.
> 
thanks Dmitry.
can you point me which file I need look into,
I am newbie in kernel. 

-- 
Xiangfu Liu
Email: xiangfu at qi-hardware dot com
Web: http://www.qi-hardware.com

Re: (matrix_keypad driver) Re: qi_lb60_keypad driver question?

[Dmitry Torokhov]

Hi Xiangfu,

On Wed, Sep 09, 2009 at 03:35:21PM +0800, Xiangfu Liu wrote:
> Dmitry Torokhov wrote:
> > Hi,
> > 
> > On Mon, Aug 31, 2009 at 12:06:42AM +0800, Xiangfu Liu wrote:
> >> Hi
> >> now the keypad in Ben NanoNote[1] is work.  problem is I don't know
> >> how to write the special assemble key of matrix_key driver. some kind
> >> of 'SHIFT', like the red key in [2].  when I press the 'RED UP POINT'
> >> + 'W' = '@'
> >>
> > 
> > Historically our KEY_* definitions did not include defines for symbols
> > like '@' because they do not have a dedicated key but rather being
> > produced as a combination of a primary key + modifier; the mapping is
> > done either in console driver or in X.
> > 
> thanks Dmitry.
> can you point me which file I need look into,

I believe you already discovered loadkeys and the keyboard maps that are
used in console mode. I believe you just need to make your 'up point'
key a modifier and make sure that 'W' with that particular modifier
emits '@'.

-- 
Dmitry

Re: (matrix_keypad driver) Re: qi_lb60_keypad driver question?

[Xiangfu Liu]

Dmitry Torokhov wrote:
> Hi Xiangfu,
> 
> On Wed, Sep 09, 2009 at 03:35:21PM +0800, Xiangfu Liu wrote:
>> Dmitry Torokhov wrote:
>>> Hi,
>>>
>>> On Mon, Aug 31, 2009 at 12:06:42AM +0800, Xiangfu Liu wrote:
>>>> Hi
>>>> now the keypad in Ben NanoNote[1] is work.  problem is I don't know
>>>> how to write the special assemble key of matrix_key driver. some kind
>>>> of 'SHIFT', like the red key in [2].  when I press the 'RED UP POINT'
>>>> + 'W' = '@'
>>>>
>>> Historically our KEY_* definitions did not include defines for symbols
>>> like '@' because they do not have a dedicated key but rather being
>>> produced as a combination of a primary key + modifier; the mapping is
>>> done either in console driver or in X.
>>>
>> thanks Dmitry.
>> can you point me which file I need look into,
> 
> I believe you already discovered loadkeys and the keyboard maps that are
> used in console mode. I believe you just need to make your 'up point'
> key a modifier and make sure that 'W' with that particular modifier
> emits '@'.
> 
the keycode 94 is the 'up point'

the loadkeys always like:
keycode 94 = Compose 
compose 'w' 'w' to '@'

it's take three keys not two.
I must press 'up point' + 'w' + 'w' then it's will display '@'.
not 'up point' + 'w' = '@'

thanks for reply.



-- 
Xiangfu Liu
Email: xiangfu at qi-hardware dot com
Web: http://www.qi-hardware.com

Re: (matrix_keypad driver) Re: qi_lb60_keypad driver question?

[Dmitry Torokhov]

On Wed, Sep 09, 2009 at 04:46:58PM +0800, Xiangfu Liu wrote:
> Dmitry Torokhov wrote:
> > Hi Xiangfu,
> > 
> > On Wed, Sep 09, 2009 at 03:35:21PM +0800, Xiangfu Liu wrote:
> >> Dmitry Torokhov wrote:
> >>> Hi,
> >>>
> >>> On Mon, Aug 31, 2009 at 12:06:42AM +0800, Xiangfu Liu wrote:
> >>>> Hi
> >>>> now the keypad in Ben NanoNote[1] is work.  problem is I don't know
> >>>> how to write the special assemble key of matrix_key driver. some kind
> >>>> of 'SHIFT', like the red key in [2].  when I press the 'RED UP POINT'
> >>>> + 'W' = '@'
> >>>>
> >>> Historically our KEY_* definitions did not include defines for symbols
> >>> like '@' because they do not have a dedicated key but rather being
> >>> produced as a combination of a primary key + modifier; the mapping is
> >>> done either in console driver or in X.
> >>>
> >> thanks Dmitry.
> >> can you point me which file I need look into,
> > 
> > I believe you already discovered loadkeys and the keyboard maps that are
> > used in console mode. I believe you just need to make your 'up point'
> > key a modifier and make sure that 'W' with that particular modifier
> > emits '@'.
> > 
> the keycode 94 is the 'up point'
> 
> the loadkeys always like:
> keycode 94 = Compose 
> compose 'w' 'w' to '@'
> 
> it's take three keys not two.
> I must press 'up point' + 'w' + 'w' then it's will display '@'.
> not 'up point' + 'w' = '@'
> 

You probably want to map your 'up point' to AltGr:

keycode 94 = AltGr
altgr keycode <w-keycode> = at

You will find additional information in 'man keymaps', also see
documentation that comes with 'kbd' package.

-- 
Dmitry