* Re: [PATCH/RFC?] usb/input: Add support for fn key on Apple PowerBooks
From: Benjamin Herrenschmidt @ 2006-01-01 6:09 UTC (permalink / raw)
To: Michael Hanselmann
Cc: linux-kernel, Dmitry Torokhov, linux-kernel, linuxppc-dev,
Vojtech Pavlik, linux-input
In-Reply-To: <20060101030331.GA26559@hansmi.ch>
On Sun, 2006-01-01 at 04:03 +0100, Michael Hanselmann wrote:
> On Sun, Jan 01, 2006 at 01:56:47PM +1100, Benjamin Herrenschmidt wrote:
> > I've been using the other patch for some time now and while it's a
> > life-saver, it does have one annoying little issue: If you press a key
> > with the Fn key down and release that key with the Fn key up, your key
> > is stuck.
>
> I noticed something like that with the numlock key as well but didn't
> have time to fix it yet.
>
> Other than that, have you found any keys that aren't mapped or are
> mapped incorrectly?
I haven't but then I haven't tested in depth neither. Such little bugs
if any can always be fixed later anyway.
> The new patch adds quite some code to hid-input.c, should it be
> configuratible via .config?
Possibly yes, since it's only useful for mac laptops...
Ben.
^ permalink raw reply
* Re: [PATCH 8/8] Add support for Xilinx ML403 reference design
From: Grant Likely @ 2006-01-02 8:00 UTC (permalink / raw)
To: Florian
In-Reply-To: <43B8DAB3.2010001@ozlabs.org>
Florian wrote:
>> I don't have a public git tree at the moment for the xilinx virtex
>> stuff. I can certainly create and maintain one if there is demand. I
>> guess it depends on how many people want to colaborate on V2Pro/V4
>> support. Anyone else interested?
>
>
> Yes. I am also working on a Virtex-4 system with Linux.
> Do you support also a Linux 2.4 tree?
Sorry, no. I'm focusing on the 2.6 stuff. IIRC, the Denx tree is
tracking the virtex support in 2.4.
Are you strictly working on 2.4? Or are you interested in 2.6 as well?
Cheers,
g.
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
(403) 663-0761
^ permalink raw reply
* Re: [PATCH 8/8] Add support for Xilinx ML403 reference design
From: David H. Lynch Jr. @ 2005-12-31 16:34 UTC (permalink / raw)
To: Grant Likely; +Cc: linuxppc-embedded
In-Reply-To: <43B601CC.1000102@secretlab.ca>
Grant Likely wrote:
> David H. Lynch Jr. wrote:
>
> Since the E-12 is a commercially available board, it would be useful to
> have the patches on the ML, even if they don't get applied to mainline.
So at what state should things be at before posting them ?
Right now:
The basic E-12 stuff is complete - though it couls use some polish. It
was based on the ML300 code, and almost certainly overlaps and conflicts
with your ML403 work. I would be happy to reconcile them, but I would
need to know what to work against.
I am not a git expert at this point. I am working against the 2.6.14.5
source3 on kernel.org. There are numerous git trees what is the right one ?
The serial/console drivers for the "Keyhole" - a bidirectional link
between a Linux/Windows development host and the E-12, and the Xilinx
UartLite are in (hopefully) late debugging, Output is probably complete,
UartLite input needs testing, Keyhole input needs alot of work - among
other things the host side is still only a display, so it is somewhat
difficult to do the Linux input side.
^ permalink raw reply
* Cross Compiling driver for PPC
From: venkatajagadeesh p @ 2006-01-02 11:52 UTC (permalink / raw)
To: linuxppc-embedded
[-- Attachment #1: Type: text/plain, Size: 306 bytes --]
Hi,
We are trying to port a newly developed device driver for powerPC . We are unable to compile it for powerpc driver on Host platform. Please give us the way to compile the device driver
---------------------------------
Yahoo! Shopping
Find Great Deals on Holiday Gifts at Yahoo! Shopping
[-- Attachment #2: Type: text/html, Size: 511 bytes --]
^ permalink raw reply
* Re: [PATCH/RFC?] usb/input: Add support for fn key on Apple PowerBooks
From: Stelian Pop @ 2006-01-02 12:06 UTC (permalink / raw)
To: Michael Hanselmann
Cc: linux-kernel, Dmitry Torokhov, linux-kernel, linuxppc-dev,
Vojtech Pavlik, linux-input
In-Reply-To: <20051231235124.GA18506@hansmi.ch>
Le dimanche 01 janvier 2006 à 00:51 +0100, Michael Hanselmann a écrit :
> On Sun, Dec 25, 2005 at 11:04:30PM -0500, Dmitry Torokhov wrote:
> > Well, we have used 11 out of 32 available bits so there still some
> > reserves. My concern is that your implementation allows only one
> > hook to be installed while with quirks you can have several of them
> > active per device.
>
> Below you find an implementation using quirks:
>
> ---
> diff -rNup linux-2.6.15-rc7.orig/drivers/usb/input/hid-core.c linux-2.6.15-rc7/drivers/usb/input/hid-core.c
> --- linux-2.6.15-rc7.orig/drivers/usb/input/hid-core.c 2006-01-01 00:41:15.000000000 +0100
> +++ linux-2.6.15-rc7/drivers/usb/input/hid-core.c 2005-12-31 22:39:53.000000000 +0100
> @@ -1580,6 +1580,10 @@ static struct hid_blacklist {
> { USB_VENDOR_ID_SAITEK, USB_DEVICE_ID_SAITEK_RUMBLEPAD, HID_QUIRK_BADPAD },
> { USB_VENDOR_ID_TOPMAX, USB_DEVICE_ID_TOPMAX_COBRAPAD, HID_QUIRK_BADPAD },
>
> + { USB_VENDOR_ID_APPLE, 0x0214, HID_QUIRK_POWERBOOK_HAS_FN },
> + { USB_VENDOR_ID_APPLE, 0x0215, HID_QUIRK_POWERBOOK_HAS_FN },
> + { USB_VENDOR_ID_APPLE, 0x0216, HID_QUIRK_POWERBOOK_HAS_FN },
> +
Works fine for me on a slightly older (jul '05) Powerbook after adding
the following USB identifiers:
+ { USB_VENDOR_ID_APPLE, 0x020E, HID_QUIRK_POWERBOOK_HAS_FN },
+ { USB_VENDOR_ID_APPLE, 0x020F, HID_QUIRK_POWERBOOK_HAS_FN },
+ { USB_VENDOR_ID_APPLE, 0x030A, HID_QUIRK_POWERBOOK_HAS_FN },
+ { USB_VENDOR_ID_APPLE, 0x030B, HID_QUIRK_POWERBOOK_HAS_FN },
Mine is a 020F but the other three ones should be fine too (those are
taken from the appletouch trackpad driver).
Stelian.
--
Stelian Pop <stelian@popies.net>
^ permalink raw reply
* Re: [PATCH] powerpc: Remove device_node addrs/n_addr
From: Olaf Hering @ 2006-01-02 13:15 UTC (permalink / raw)
To: Benjamin Herrenschmidt; +Cc: linuxppc-dev list
In-Reply-To: <1134457283.6989.185.camel@gaston>
On Tue, Dec 13, Benjamin Herrenschmidt wrote:
> The pre-parsed addrs/n_addrs fields in struct device_node are finally
> gone. Remove the dodgy heuristics that did that parsing at boot and
> remove the fields themselves since we now have a good replacement with
> the new OF parsing code. This patch also fixes a bunch of drivers to use
> the new code instead, so that at least pmac32, pseries, iseries and g5
> defconfigs build.
> +++ linux-work/include/asm-powerpc/prom.h 2005-12-13 17:51:20.000000000 +1100
> @@ -120,8 +82,6 @@ struct device_node {
> char *type;
> phandle node;
> phandle linux_phandle;
> - int n_addrs;
> - struct address_range *addrs;
> int n_intrs;
> struct interrupt_info *intrs;
> char *full_name;
Is this patch supposed to be complete? I will find references to n_addrs
in arch/powerpc:
hydra_init, chrp_find_bridges, chrp_find_openpic, comment in
of_finish_dynamic_node.
--
short story of a lazy sysadmin:
alias appserv=wotan
^ permalink raw reply
* ELDK 4.0
From: HappyPhot @ 2006-01-02 14:29 UTC (permalink / raw)
To: linuxppc-embedded
Dear group,
Can anybody tell how to get ELDK 4.0 ?
I seems need to go to somewhere to get the
source code to compile, right? Could you give
me a way ?
thank you,
/HappyPhot
^ permalink raw reply
* VFS: Cannot open root device "31:03" or unknown-block(31,3)
From: HappyPhot @ 2006-01-02 14:48 UTC (permalink / raw)
To: linuxppc-embedded
Hi,
I've suffered for many days and "google" almost every where.
I would like to boot from the flash with jffs2 (i.e. using jffs2 as my
root /) . But it alyaws shows:
VFS: Cannot open root device..... (whole message is as below)
Anybody knows what may cause this ? Please help and
thank you.
/HappyPhot
==============(booting message)==================
.......
physmap flash device: 1000000 at 70000000
phys_mapped_flash: Found 2 x8 devices at 0x0 in 16-bit bank
Intel/Sharp Extended Query Table at 0x0031
Using buffer write method
cfi_cmdset_0001: Erase suspend on write enabled
5 cmdlinepart partitions found on MTD device phys_mapped_flash
Creating 5 MTD partitions on "phys_mapped_flash":
0x00000000-0x00200000 : "k4"
mtd: Giving out device 0 to k4
0x00200000-0x00400000 : "k6"
mtd: Giving out device 1 to k6
0x00400000-0x00800000 : "rd"
mtd: Giving out device 2 to rd
0x00800000-0x00c00000 : "jffs2"
mtd: Giving out device 3 to jffs2
0x00c00000-0x02000000 : "others"
mtd: Giving out device 4 to others
VFS: Cannot open root device "31:03" or unknown-block(31,3)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(31,3)
<0>Rebooting in 180 seconds..
==========================================
^ permalink raw reply
* Re: VFS: Cannot open root device "31:03" or unknown-block(31,3)
From: David Jander @ 2006-01-02 15:57 UTC (permalink / raw)
To: linuxppc-embedded; +Cc: HappyPhot
In-Reply-To: <000701c60fab$9fdca6a0$0760120a@photon>
On Monday 02 January 2006 15:48, HappyPhot wrote:
> Hi,
> I've suffered for many days and "google" almost every where.
> I would like to boot from the flash with jffs2 (i.e. using jffs2 as my
> root /) . But it alyaws shows:
> VFS: Cannot open root device..... (whole message is as below)
>
> Anybody knows what may cause this ? Please help and
> thank you.
>[...]
You omitted the interesting part of the log output, the bootarguments at the
very beginning. What is the value of root= ?
Maybe you made the typical mistake of specifying /dev/mtd3 instead
of /dev/mtdblock3, or you didn't compile in support for mtd access as a block
device?
Greetings,
--
David Jander
^ permalink raw reply
* Re: [PATCH 8/8] Add support for Xilinx ML403 reference design
From: Grant Likely @ 2006-01-02 16:26 UTC (permalink / raw)
To: David H. Lynch Jr.; +Cc: linuxppc-embedded
In-Reply-To: <43B6B32A.5060606@dlasys.net>
David H. Lynch Jr. wrote:
> Grant Likely wrote:
>
>>David H. Lynch Jr. wrote:
>
>
>>Since the E-12 is a commercially available board, it would be useful to
>>have the patches on the ML, even if they don't get applied to mainline.
>
>
> So at what state should things be at before posting them ?
>
> Right now:
> The basic E-12 stuff is complete - though it couls use some polish. It
> was based on the ML300 code, and almost certainly overlaps and conflicts
> with your ML403 work. I would be happy to reconcile them, but I would
> need to know what to work against.
If you want initial comments, then don't worry about polish; Send your
raw diff (in unified format please!) and put [RFC] in the subject line
so nobody mistakes it as stable code. :) I'll happily comment on it.
I'm sure it conflicts with my ML403 work considering I've moved from the
OCP to the platform bus.
>
> I am not a git expert at this point.
Neither am I. :)
Try this:
install GIT: http://linux.yyz.us/git-howto.html#installing_git
install Cogito: http://www.kernel.org/pub/software/scm/cogito/README
easy user guide: http://wellington.pm.org/archive/200510/git/
> I am working against the 2.6.14.5
> source3 on kernel.org. There are numerous git trees what is the right one ?
I'm using Linus's tree, seeked to tag v2.6.14.
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
>
>
> The serial/console drivers for the "Keyhole" - a bidirectional link
> between a Linux/Windows development host and the E-12, and the Xilinx
> UartLite are in (hopefully) late debugging, Output is probably complete,
> UartLite input needs testing, Keyhole input needs alot of work - among
> other things the host side is still only a display, so it is somewhat
> difficult to do the Linux input side.
>
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
(403) 663-0761
^ permalink raw reply
* Re: [PATCH] powerpc: Remove device_node addrs/n_addr
From: Benjamin Herrenschmidt @ 2006-01-02 22:01 UTC (permalink / raw)
To: Olaf Hering; +Cc: linuxppc-dev list
In-Reply-To: <20060102131539.GA12434@suse.de>
On Mon, 2006-01-02 at 14:15 +0100, Olaf Hering wrote:
> On Tue, Dec 13, Benjamin Herrenschmidt wrote:
>
> > The pre-parsed addrs/n_addrs fields in struct device_node are finally
> > gone. Remove the dodgy heuristics that did that parsing at boot and
> > remove the fields themselves since we now have a good replacement with
> > the new OF parsing code. This patch also fixes a bunch of drivers to use
> > the new code instead, so that at least pmac32, pseries, iseries and g5
> > defconfigs build.
>
> > +++ linux-work/include/asm-powerpc/prom.h 2005-12-13 17:51:20.000000000 +1100
>
> > @@ -120,8 +82,6 @@ struct device_node {
> > char *type;
> > phandle node;
> > phandle linux_phandle;
> > - int n_addrs;
> > - struct address_range *addrs;
> > int n_intrs;
> > struct interrupt_info *intrs;
> > char *full_name;
>
> Is this patch supposed to be complete? I will find references to n_addrs
> in arch/powerpc:
>
> hydra_init, chrp_find_bridges, chrp_find_openpic, comment in
> of_finish_dynamic_node.
No, it's complete as far as powermac is concerned. I'll deal with the
remaining bits this week.
Ben.
^ permalink raw reply
* Re: [PATCH/RFC?] usb/input: Add support for fn key on Apple PowerBooks
From: Michael Hanselmann @ 2006-01-02 22:46 UTC (permalink / raw)
To: Benjamin Herrenschmidt
Cc: linux-kernel, Dmitry Torokhov, linux-kernel, linuxppc-dev,
Vojtech Pavlik, linux-input
In-Reply-To: <1136084207.4635.86.camel@localhost.localdomain>
On Sun, Jan 01, 2006 at 01:56:47PM +1100, Benjamin Herrenschmidt wrote:
> I've been using the other patch for some time now and while it's a
> life-saver, it does have one annoying little issue: If you press a key
> with the Fn key down and release that key with the Fn key up, your key
> is stuck.
Here's another patch with this and some other issues fixed.
Signed-off-by: Michael Hanselmann <linux-kernel@hansmi.ch>
Acked-by: Rene Nussbaumer <linux-kernel@killerfox.forkbomb.ch>
Acked-by: Johannes Berg <johannes@sipsolutions.net>
Acked-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
---
diff -rNup linux-2.6.15-rc7.orig/drivers/usb/input/Kconfig linux-2.6.15-rc7/drivers/usb/input/Kconfig
--- linux-2.6.15-rc7.orig/drivers/usb/input/Kconfig 2006-01-01 00:41:15.000000000 +0100
+++ linux-2.6.15-rc7/drivers/usb/input/Kconfig 2006-01-02 20:26:21.000000000 +0100
@@ -37,6 +37,16 @@ config USB_HIDINPUT
If unsure, say Y.
+config USB_HIDINPUT_POWERBOOK
+ bool "Enable support for iBook/PowerBook special keys"
+ default n
+ depends on USB_HIDINPUT
+ help
+ Say Y here if you want support for the special keys (Fn, Numlock) on
+ Apple iBooks and PowerBooks.
+
+ If unsure, say N.
+
config HID_FF
bool "Force feedback support (EXPERIMENTAL)"
depends on USB_HIDINPUT && EXPERIMENTAL
diff -rNup linux-2.6.15-rc7.orig/drivers/usb/input/hid-core.c linux-2.6.15-rc7/drivers/usb/input/hid-core.c
--- linux-2.6.15-rc7.orig/drivers/usb/input/hid-core.c 2006-01-01 00:41:15.000000000 +0100
+++ linux-2.6.15-rc7/drivers/usb/input/hid-core.c 2006-01-02 13:52:59.000000000 +0100
@@ -1580,6 +1580,14 @@ static struct hid_blacklist {
{ USB_VENDOR_ID_SAITEK, USB_DEVICE_ID_SAITEK_RUMBLEPAD, HID_QUIRK_BADPAD },
{ USB_VENDOR_ID_TOPMAX, USB_DEVICE_ID_TOPMAX_COBRAPAD, HID_QUIRK_BADPAD },
+ { USB_VENDOR_ID_APPLE, 0x020E, HID_QUIRK_POWERBOOK_HAS_FN },
+ { USB_VENDOR_ID_APPLE, 0x020F, HID_QUIRK_POWERBOOK_HAS_FN },
+ { USB_VENDOR_ID_APPLE, 0x0214, HID_QUIRK_POWERBOOK_HAS_FN },
+ { USB_VENDOR_ID_APPLE, 0x0215, HID_QUIRK_POWERBOOK_HAS_FN },
+ { USB_VENDOR_ID_APPLE, 0x0216, HID_QUIRK_POWERBOOK_HAS_FN },
+ { USB_VENDOR_ID_APPLE, 0x030A, HID_QUIRK_POWERBOOK_HAS_FN },
+ { USB_VENDOR_ID_APPLE, 0x030B, HID_QUIRK_POWERBOOK_HAS_FN },
+
{ 0, 0 }
};
diff -rNup linux-2.6.15-rc7.orig/drivers/usb/input/hid-input.c linux-2.6.15-rc7/drivers/usb/input/hid-input.c
--- linux-2.6.15-rc7.orig/drivers/usb/input/hid-input.c 2006-01-01 00:41:15.000000000 +0100
+++ linux-2.6.15-rc7/drivers/usb/input/hid-input.c 2006-01-02 23:35:36.000000000 +0100
@@ -63,6 +63,70 @@ static struct {
__s32 y;
} hid_hat_to_axis[] = {{ 0, 0}, { 0,-1}, { 1,-1}, { 1, 0}, { 1, 1}, { 0, 1}, {-1, 1}, {-1, 0}, {-1,-1}};
+struct hidinput_key_translation {
+ u16 from;
+ u16 to;
+ u8 flags;
+};
+
+#ifdef CONFIG_USB_HIDINPUT_POWERBOOK
+
+#define POWERBOOK_FLAG_FKEY 0x01
+
+static struct hidinput_key_translation powerbook_fn_keys[] = {
+ { KEY_BACKSPACE, KEY_DELETE },
+ { KEY_F1, KEY_BRIGHTNESSDOWN, POWERBOOK_FLAG_FKEY },
+ { KEY_F2, KEY_BRIGHTNESSUP, POWERBOOK_FLAG_FKEY },
+ { KEY_F3, KEY_MUTE, POWERBOOK_FLAG_FKEY },
+ { KEY_F4, KEY_VOLUMEDOWN, POWERBOOK_FLAG_FKEY },
+ { KEY_F5, KEY_VOLUMEUP, POWERBOOK_FLAG_FKEY },
+ { KEY_F6, KEY_NUMLOCK, POWERBOOK_FLAG_FKEY },
+ { KEY_F7, KEY_SWITCHVIDEOMODE, POWERBOOK_FLAG_FKEY },
+ { KEY_F8, KEY_KBDILLUMTOGGLE, POWERBOOK_FLAG_FKEY },
+ { KEY_F9, KEY_KBDILLUMDOWN, POWERBOOK_FLAG_FKEY },
+ { KEY_F10, KEY_KBDILLUMUP, POWERBOOK_FLAG_FKEY },
+ { KEY_UP, KEY_PAGEUP },
+ { KEY_DOWN, KEY_PAGEDOWN },
+ { KEY_LEFT, KEY_HOME },
+ { KEY_RIGHT, KEY_END },
+ { }
+};
+
+static struct hidinput_key_translation powerbook_numlock_keys[] = {
+ { KEY_J, KEY_KP1 },
+ { KEY_K, KEY_KP2 },
+ { KEY_L, KEY_KP3 },
+ { KEY_U, KEY_KP4 },
+ { KEY_I, KEY_KP5 },
+ { KEY_O, KEY_KP6 },
+ { KEY_7, KEY_KP7 },
+ { KEY_8, KEY_KP8 },
+ { KEY_9, KEY_KP9 },
+ { KEY_M, KEY_KP0 },
+ { KEY_DOT, KEY_KPDOT },
+ { KEY_SLASH, KEY_KPPLUS },
+ { KEY_SEMICOLON, KEY_KPMINUS },
+ { KEY_P, KEY_KPASTERISK },
+ { KEY_MINUS, KEY_KPEQUAL },
+ { KEY_0, KEY_KPSLASH },
+ { KEY_ENTER, KEY_KPENTER },
+ { KEY_F6, KEY_NUMLOCK },
+ { }
+};
+
+static int powerbook_fkeysfirst = 1;
+module_param_named(pb_fkeysfirst, powerbook_fkeysfirst, bool, 0644);
+MODULE_PARM_DESC(powerbook_fkeysfirst, "Use fn special keys only while pressing fn");
+
+static int powerbook_enablefnkeys = 1;
+module_param_named(pb_enablefnkeys, powerbook_enablefnkeys, bool, 0644);
+MODULE_PARM_DESC(powerbook_enablefnkeys, "Enable fn special keys");
+
+static int powerbook_enablekeypad = 1;
+module_param_named(pb_enablekeypad, powerbook_enablekeypad, bool, 0644);
+MODULE_PARM_DESC(powerbook_enablekeypad, "Enable keypad keys");
+#endif
+
#define map_abs(c) do { usage->code = c; usage->type = EV_ABS; bit = input->absbit; max = ABS_MAX; } while (0)
#define map_rel(c) do { usage->code = c; usage->type = EV_REL; bit = input->relbit; max = REL_MAX; } while (0)
#define map_key(c) do { usage->code = c; usage->type = EV_KEY; bit = input->keybit; max = KEY_MAX; } while (0)
@@ -73,6 +137,85 @@ static struct {
#define map_key_clear(c) do { map_key(c); clear_bit(c, bit); } while (0)
#define map_ff_effect(c) do { set_bit(c, input->ffbit); } while (0)
+static inline struct hidinput_key_translation *find_translation(
+ struct hidinput_key_translation *table, int from)
+{
+ struct hidinput_key_translation *trans;
+
+ /* Look for the translation */
+ for(trans = table; trans->from && !(trans->from == from); trans++);
+
+ return (trans->from?trans:NULL);
+}
+
+static int hidinput_pb_event(struct hid_device *hid, struct input_dev *input,
+ struct hid_usage *usage, __s32 value)
+{
+#ifdef CONFIG_USB_HIDINPUT_POWERBOOK
+ struct hidinput_key_translation *trans;
+
+ if (usage->code == KEY_FN) {
+ if (value) hid->quirks |= HID_QUIRK_POWERBOOK_FN_ON;
+ else hid->quirks &= ~HID_QUIRK_POWERBOOK_FN_ON;
+
+ input_event(input, usage->type, usage->code, value);
+
+ return 1;
+ }
+
+ if (powerbook_enablefnkeys) {
+ trans = find_translation(powerbook_fn_keys, usage->code);
+
+ if (trans) {
+ int do_translate;
+
+ if (test_bit(usage->code, hid->pb_fn))
+ do_translate = 1;
+ else if (trans->flags & POWERBOOK_FLAG_FKEY)
+ do_translate =
+ ( powerbook_fkeysfirst && (hid->quirks & HID_QUIRK_POWERBOOK_FN_ON)) ||
+ (!powerbook_fkeysfirst && !(hid->quirks & HID_QUIRK_POWERBOOK_FN_ON));
+ else
+ do_translate = (hid->quirks & HID_QUIRK_POWERBOOK_FN_ON);
+
+ if (do_translate) {
+ if (value)
+ set_bit(usage->code, hid->pb_fn);
+ else
+ clear_bit(usage->code, hid->pb_fn);
+
+ input_event(input, usage->type, trans->to, value);
+
+ return 1;
+ }
+ }
+ }
+
+ if (powerbook_enablekeypad) {
+ int try_translate =
+ test_bit(usage->code, hid->pb_numlock)?1:
+ test_bit(LED_NUML, input->led);
+
+ if (try_translate) {
+ trans = find_translation(powerbook_numlock_keys, usage->code);
+
+ if (trans) {
+ if (value)
+ set_bit(usage->code, hid->pb_numlock);
+ else
+ clear_bit(usage->code, hid->pb_numlock);
+
+ input_event(input, usage->type, trans->to, value);
+ }
+
+ return 1;
+ }
+ }
+#endif
+
+ return 0;
+}
+
static void hidinput_configure_usage(struct hid_input *hidinput, struct hid_field *field,
struct hid_usage *usage)
{
@@ -325,7 +468,27 @@ static void hidinput_configure_usage(str
set_bit(EV_REP, input->evbit);
switch(usage->hid & HID_USAGE) {
- case 0x003: map_key_clear(KEY_FN); break;
+#ifdef CONFIG_USB_HIDINPUT_POWERBOOK
+ /* The fn key on Apple PowerBooks */
+ case 0x0003: {
+ struct hidinput_key_translation *trans;
+
+ map_key_clear(KEY_FN);
+
+ set_bit(KEY_FN, input->keybit);
+ set_bit(KEY_NUMLOCK, input->keybit);
+
+ /* Enable all needed keys */
+ for(trans = powerbook_fn_keys; trans->from; trans++)
+ set_bit(trans->to, input->keybit);
+
+ for(trans = powerbook_numlock_keys; trans->from; trans++)
+ set_bit(trans->to, input->keybit);
+
+ goto ignore;
+ }
+#endif
+
default: goto ignore;
}
break;
@@ -482,6 +645,11 @@ void hidinput_hid_event(struct hid_devic
return;
}
+ if ((hid->quirks & HID_QUIRK_POWERBOOK_HAS_FN) &&
+ hidinput_pb_event(hid, input, usage, value)) {
+ return;
+ }
+
if (usage->hat_min < usage->hat_max || usage->hat_dir) {
int hat_dir = usage->hat_dir;
if (!hat_dir)
diff -rNup linux-2.6.15-rc7.orig/drivers/usb/input/hid.h linux-2.6.15-rc7/drivers/usb/input/hid.h
--- linux-2.6.15-rc7.orig/drivers/usb/input/hid.h 2006-01-01 00:41:15.000000000 +0100
+++ linux-2.6.15-rc7/drivers/usb/input/hid.h 2006-01-02 21:44:15.000000000 +0100
@@ -246,6 +246,8 @@ struct hid_item {
#define HID_QUIRK_2WHEEL_MOUSE_HACK_5 0x100
#define HID_QUIRK_2WHEEL_MOUSE_HACK_ON 0x200
#define HID_QUIRK_2WHEEL_POWERMOUSE 0x400
+#define HID_QUIRK_POWERBOOK_HAS_FN 0x0000800
+#define HID_QUIRK_POWERBOOK_FN_ON 0x0001000
/*
* This is the global environment of the parser. This information is
@@ -431,6 +433,14 @@ struct hid_device { /* device repo
void (*ff_exit)(struct hid_device*); /* Called by hid_exit_ff(hid) */
int (*ff_event)(struct hid_device *hid, struct input_dev *input,
unsigned int type, unsigned int code, int value);
+
+#ifdef CONFIG_USB_HIDINPUT_POWERBOOK
+ /* We do this here because it's only relevant for the
+ * USB devices, not for all input_dev's.
+ */
+ unsigned long pb_fn[NBITS(KEY_MAX)];
+ unsigned long pb_numlock[NBITS(KEY_MAX)];
+#endif
};
#define HID_GLOBAL_STACK_SIZE 4
^ permalink raw reply
* Re: VFS: Cannot open root device "31:03" or unknown-block(31,3)
From: HappyPhot @ 2006-01-03 2:48 UTC (permalink / raw)
To: David Jander, linuxppc-embedded
In-Reply-To: <200601021657.35359.david.jander@protonic.nl>
> On Monday 02 January 2006 15:48, HappyPhot wrote:
>> Hi,
>> I've suffered for many days and "google" almost every where.
>> I would like to boot from the flash with jffs2 (i.e. using jffs2 as my
>> root /) . But it alyaws shows:
>> VFS: Cannot open root device..... (whole message is as below)
>>
>> Anybody knows what may cause this ? Please help and
>> thank you.
>>[...]
>
> You omitted the interesting part of the log output, the bootarguments at
> the
> very beginning. What is the value of root= ?
> Maybe you made the typical mistake of specifying /dev/mtd3 instead
> of /dev/mtdblock3, or you didn't compile in support for mtd access as a
> block
> device?
>
Hi, David and all,
I've tried root=/dev/mtdblock3, root=/dev/mtd3, root=31:03 etc. And
"Caching
block device access to MTD devices" was also selected when 'make
menuconfig'.
The results were the same.
I use "phys_mapped_flash" and "mtdparts=phys_mapped_flash:2M(k4),2M(k6),
4M(rd),4M(jffs2),-(User_Data)". What is the "root=" I should use ?
Also, I am wondering how the kernel knows "/dev/mtdblock3" is in my flash
?
I think I never do any setting about this....
thank you ,
/HappyPhot
^ permalink raw reply
* Re: [PATCH/RFC?] usb/input: Add support for fn key on Apple PowerBooks
From: Ben Collins @ 2006-01-03 2:29 UTC (permalink / raw)
To: Michael Hanselmann
Cc: linux-kernel, Dmitry Torokhov, linux-kernel, linuxppc-dev,
Vojtech Pavlik, linux-input
In-Reply-To: <20060102224640.GB27317@hansmi.ch>
On Mon, 2006-01-02 at 23:46 +0100, Michael Hanselmann wrote:
> +static int powerbook_fkeysfirst = 1;
> +module_param_named(pb_fkeysfirst, powerbook_fkeysfirst, bool, 0644);
> +MODULE_PARM_DESC(powerbook_fkeysfirst, "Use fn special keys only while pressing fn");
> +
> +static int powerbook_enablefnkeys = 1;
> +module_param_named(pb_enablefnkeys, powerbook_enablefnkeys, bool, 0644);
> +MODULE_PARM_DESC(powerbook_enablefnkeys, "Enable fn special keys");
> +
> +static int powerbook_enablekeypad = 1;
> +module_param_named(pb_enablekeypad, powerbook_enablekeypad, bool, 0644);
> +MODULE_PARM_DESC(powerbook_enablekeypad, "Enable keypad keys");
> +#endif
I think these should be inverted to, something like
pbook_disable_keypad, pbook_disable_fnkeys and pbook_fnfirst.
Two reasons. First, it just makes more sense to pass a module param to
turn something on (doing powerbook_enablekeypad=0 isn't as intuitive as
pbook_disable_keypad=1). Second reason is that since these are static
vars, defaulting them to uninitialized (leaving them in the bss, as 0)
reduces binary size.
--
Ben Collins <ben.collins@ubuntu.com>
Developer
Ubuntu Linux
^ permalink raw reply
* Custom Driver
From: Brett McNerney @ 2006-01-03 3:43 UTC (permalink / raw)
To: linuxppc-embedded
[-- Attachment #1: Type: text/plain, Size: 438 bytes --]
I am need to create a driver to interface to custom hardware on a ml403
board. I am first trying to just create a ipif register bank and access the
registers from linux but am not having any luck of yet. Has anyone
successfully done this and if so explain how or supply a driver to do this
and how to build it into the kernel? I am new at this and am having great
difficutly right now.
Thanks for any help anyone can supply
Brett
[-- Attachment #2: Type: text/html, Size: 2064 bytes --]
^ permalink raw reply
* Re: Custom Driver
From: Grant Likely @ 2006-01-03 3:59 UTC (permalink / raw)
To: Brett McNerney; +Cc: linuxppc-embedded
In-Reply-To: <000101c61017$ec64d080$0202a8c0@lilmac>
Brett McNerney wrote:
> I am need to create a driver to interface to custom hardware on a ml403
> board. I am first trying to just create a ipif register bank and access
> the registers from linux but am not having any luck of yet. Has anyone
> successfully done this and if so explain how or supply a driver to do
> this and how to build it into the kernel? I am new at this and am
> having great difficutly right now.
>
> Thanks for any help anyone can supply
Can you access your device from a debugger, or a no-os program (like a
bootloader)? Did you call ioremap() to map the physical register
address into virtual memory? Can you give more detail?
g.
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
(403) 663-0761
^ permalink raw reply
* Re: [PATCH 8/8] Add support for Xilinx ML403 reference design
From: Grant Likely @ 2006-01-03 8:08 UTC (permalink / raw)
To: Florian
In-Reply-To: <43BA2944.5030903@ozlabs.org>
Florian wrote:
>>> Yes. I am also working on a Virtex-4 system with Linux.
>>> Do you support also a Linux 2.4 tree?
>>
>>
>> Sorry, no. I'm focusing on the 2.6 stuff. IIRC, the Denx tree is
>> tracking the virtex support in 2.4.
>>
>> Are you strictly working on 2.4? Or are you interested in 2.6 as well?
>
>
> I am working with the Montavista 2.4 sources.
> 2.6 is also possible but I read 2.6 is not better than 2.4 for embedded
> systems.
> We didn't make a final decision so you can convince me to try 2.6.
Nah, that sounds like to much work. :) Choose what works for you. If
2.4 has the features you need then go for it. (just keep in mind that
most new development it focused on 2.6)
g.
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
(403) 663-0761
^ permalink raw reply
* Re: [PATCH 8/8] Add support for Xilinx ML403 reference design
From: Paula Saameño @ 2006-01-03 8:12 UTC (permalink / raw)
To: linuxppc-embedded
[-- Attachment #1: Type: text/plain, Size: 739 bytes --]
I am working with ML403 as well. Right now, I am using a 2.4.26 kernel, but
I would be interested in a 2.6 one, it would be great!!
Happy 2006!!
Paula Saameno
Florian wrote:
>> I don't have a public git tree at the moment for the xilinx virtex
>> stuff. I can certainly create and maintain one if there is demand. I
>> guess it depends on how many people want to colaborate on V2Pro/V4
>> support. Anyone else interested?
>
>
> Yes. I am also working on a Virtex-4 system with Linux.
> Do you support also a Linux 2.4 tree?
Sorry, no. I'm focusing on the 2.6 stuff. IIRC, the Denx tree is
tracking the virtex support in 2.4.
Are you strictly working on 2.4? Or are you interested in 2.6 as well?
Cheers,
g.
[-- Attachment #2: Type: text/html, Size: 889 bytes --]
^ permalink raw reply
* Re: [PATCH 8/8] Add support for Xilinx ML403 reference design
From: Grant Likely @ 2006-01-03 8:24 UTC (permalink / raw)
To: Paula Saameño; +Cc: linuxppc-embedded
In-Reply-To: <259581790601030012u1ec195c2n7f42766d443548c2@mail.gmail.com>
Paula Saameño wrote:
> I am working with ML403 as well. Right now, I am using a 2.4.26 kernel,
> but I would be interested in a 2.6 one, it would be great!!
>
> Happy 2006!!
> Paula Saameno
Thanks Paula.
Can you try the posted patches on your ML403? It should compile and
boot with no problems with the reference design. (However, I got the
memory size initialization wrong; add mem=64M to the kernel command line)
I'll send a patch to fix the mem size tomorrow.
Thanks,
g.
>
> Florian wrote:
>>> I don't have a public git tree at the moment for the xilinx virtex
>>> stuff. I can certainly create and maintain one if there is demand. I
>>> guess it depends on how many people want to colaborate on V2Pro/V4
>>> support. Anyone else interested?
>>
>>
>> Yes. I am also working on a Virtex-4 system with Linux.
>> Do you support also a Linux 2.4 tree?
> Sorry, no. I'm focusing on the 2.6 stuff. IIRC, the Denx tree is
> tracking the virtex support in 2.4.
>
> Are you strictly working on 2.4? Or are you interested in 2.6 as well?
>
> Cheers,
> g.
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
(403) 663-0761
^ permalink raw reply
* Re: [PATCH 8/8] Add support for Xilinx ML403 reference design
From: Paula Saameño @ 2006-01-03 8:29 UTC (permalink / raw)
To: Grant Likely; +Cc: linuxppc-embedded
In-Reply-To: <43BA34C5.9050609@secretlab.ca>
[-- Attachment #1: Type: text/plain, Size: 1682 bytes --]
Hi Grant,
I´ll try the patches today and I let you know how is going.
See you!
On 1/3/06, Grant Likely <grant.likely@secretlab.ca> wrote:
>
> Paula Saameño wrote:
> > I am working with ML403 as well. Right now, I am using a 2.4.26 kernel,
> > but I would be interested in a 2.6 one, it would be great!!
> >
> > Happy 2006!!
> > Paula Saameno
>
> Thanks Paula.
>
> Can you try the posted patches on your ML403? It should compile and
> boot with no problems with the reference design. (However, I got the
> memory size initialization wrong; add mem=64M to the kernel command line)
>
> I'll send a patch to fix the mem size tomorrow.
>
> Thanks,
> g.
>
> >
> > Florian wrote:
> >>> I don't have a public git tree at the moment for the xilinx virtex
> >>> stuff. I can certainly create and maintain one if there is demand. I
> >>> guess it depends on how many people want to colaborate on V2Pro/V4
> >>> support. Anyone else interested?
> >>
> >>
> >> Yes. I am also working on a Virtex-4 system with Linux.
> >> Do you support also a Linux 2.4 tree?
> > Sorry, no. I'm focusing on the 2.6 stuff. IIRC, the Denx tree is
> > tracking the virtex support in 2.4.
> >
> > Are you strictly working on 2.4? Or are you interested in 2.6 as well?
> >
> > Cheers,
> > g.
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Linuxppc-embedded mailing list
> > Linuxppc-embedded@ozlabs.org
> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>
> --
> Grant Likely, B.Sc. P.Eng.
> Secret Lab Technologies Ltd.
> (403) 663-0761
>
[-- Attachment #2: Type: text/html, Size: 2318 bytes --]
^ permalink raw reply
* Re: [PATCH 8/8] Add support for Xilinx ML403 reference design
From: Grant Likely @ 2006-01-03 8:30 UTC (permalink / raw)
To: Paula Saameño; +Cc: linuxppc-embedded
In-Reply-To: <259581790601030029j6fa915f9nfb3869ad41915aa4@mail.gmail.com>
Paula Saameño wrote:
> Hi Grant,
>
> I´ll try the patches today and I let you know how is going.
BTW, 'make ml403_defconfig' should work
>
> See you!
>
> On 1/3/06, *Grant Likely* <grant.likely@secretlab.ca
> <mailto:grant.likely@secretlab.ca>> wrote:
>
> Paula Saameño wrote:
> > I am working with ML403 as well. Right now, I am using a 2.4.26
> kernel,
> > but I would be interested in a 2.6 one, it would be great!!
> >
> > Happy 2006!!
> > Paula Saameno
>
> Thanks Paula.
>
> Can you try the posted patches on your ML403? It should compile and
> boot with no problems with the reference design. (However, I got the
> memory size initialization wrong; add mem=64M to the kernel command
> line)
>
> I'll send a patch to fix the mem size tomorrow.
>
> Thanks,
> g.
>
> >
> > Florian wrote:
> >>> I don't have a public git tree at the moment for the xilinx virtex
> >>> stuff. I can certainly create and maintain one if there is
> demand. I
> >>> guess it depends on how many people want to colaborate on V2Pro/V4
> >>> support. Anyone else interested?
> >>
> >>
> >> Yes. I am also working on a Virtex-4 system with Linux.
> >> Do you support also a Linux 2.4 tree?
> > Sorry, no. I'm focusing on the 2.6 stuff. IIRC, the Denx tree is
> > tracking the virtex support in 2.4.
> >
> > Are you strictly working on 2.4? Or are you interested in 2.6 as
> well?
> >
> > Cheers,
> > g.
> >
> >
> >
> ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Linuxppc-embedded mailing list
> > Linuxppc-embedded@ozlabs.org <mailto:Linuxppc-embedded@ozlabs.org>
> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>
> --
> Grant Likely, B.Sc. P.Eng.
> Secret Lab Technologies Ltd.
> (403) 663-0761
>
>
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
(403) 663-0761
^ permalink raw reply
* Re: mv643xx_eth, sleeping function called from invalid context at mm/slab.c:2472
From: Olaf Hering @ 2006-01-03 9:54 UTC (permalink / raw)
To: Dale Farnsworth; +Cc: linuxppc-dev
In-Reply-To: <20051228224937.GA6320@xyzzy.farnsworth.org>
On Wed, Dec 28, Dale Farnsworth wrote:
> (For unknown reasons, I didn't receive this message directly from the
> mailing list, and the archive doesn't seem to have message-ids, so
> I can't supply a References: header.)
This doesnt help:
MV-643xx 10/100/1000 Ethernet Driver
eth1: port 1 with MAC address 00:2b:2f:de:ad:01
eth1: Scatter Gather Enabled
eth1: TX TCP/IP Checksumming Supported
eth1: RX TCP/UDP Checksum Offload ON
eth1: RX NAPI Enabled
eth1: Using SRAM
Debug: sleeping function called from invalid context at mm/slab.c:2472
in_atomic():0, irqs_disabled():1
Call Trace:
[C3E01D40] [C000BCAC] show_stack+0x54/0x184 (unreliable)
[C3E01D60] [C0028E68] __might_sleep+0xbc/0xd0
[C3E01D70] [C005FD3C] __kmalloc+0x88/0x158
[C3E01D90] [D2281264] mv643xx_eth_real_open+0x15c/0x4b4 [mv643xx_eth]
[C3E01DC0] [D22820C0] mv643xx_eth_open+0x68/0xb0 [mv643xx_eth]
[C3E01DE0] [C025638C] dev_open+0x70/0xd8
[C3E01E00] [C02544F8] dev_change_flags+0x6c/0x13c
[C3E01E20] [C02A1838] devinet_ioctl+0x280/0x708
[C3E01E80] [C02A21BC] inet_ioctl+0xb4/0x100
[C3E01E90] [C02BF1A0] packet_ioctl+0x15c/0x188
[C3E01EB0] [C024A9A8] sock_ioctl+0x30c/0x334
[C3E01ED0] [C0093350] do_ioctl+0x3c/0x88
[C3E01EE0] [C0093784] vfs_ioctl+0x3e8/0x424
[C3E01F10] [C0093828] sys_ioctl+0x68/0x98
[C3E01F40] [C0010A60] ret_from_syscall+0x0/0x4c
--- Exception: c01 at 0x7f666e8
LR = 0x7f66680
eth1: no IPv6 routers present
--
short story of a lazy sysadmin:
alias appserv=wotan
^ permalink raw reply
* Re: Re: Custom Driver
From: andreas_schmidt @ 2006-01-03 12:16 UTC (permalink / raw)
To: Grant Likely; +Cc: linuxppc-embedded
In-Reply-To: <43B9F69B.6090407@secretlab.ca>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
>Brett McNerney wrote:
>> I am need to create a driver to interface to custom hardware on a ml403
>> board. I am first trying to just create a ipif register bank and
access
>> the registers from linux but am not having any luck of yet. Has anyone
>> successfully done this and if so explain how or supply a driver to do
>> this and how to build it into the kernel? I am new at this and am
>> having great difficutly right now.
>>
>> Thanks for any help anyone can supply
>Can you access your device from a debugger, or a no-os program (like a
>bootloader)? Did you call ioremap() to map the physical register
>address into virtual memory? Can you give more detail?
I have already wrote I custom driver for Xilinx FPGA.
For this I have looked to already exist driver for Xilinx in Linux tree
and modify them for me.
It was no problem then.
g.
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
(403) 663-0761
[-- Attachment #2: Type: text/html, Size: 1231 bytes --]
^ permalink raw reply
* "argument list too long"
From: Noé SERRES @ 2006-01-03 14:06 UTC (permalink / raw)
To: Linuxppc-embedded
[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]
Hi,
I'm trying to compile a kernel for an embedded-powerpc-linux application.
As a first step/training, I followed closely the instructions of the
document "The DENX U-Boot and Linux Guide" for a TQM8XXL board, that is to
say:
bash$ mrproper
bash$ make TQM823L_config
bash$ make oldconfig
bash$ make dep
After a few minutes of dependency creation, I get the following error
"argument list too long":
scripts/mkdep -- `find
/usr/src/linuxppc_2_4_devel-2005-10-25-1440/include/asm
/usr/src/linuxppc_2_4
_devel-2005-10-25-1440/include/linux
/usr/src/linuxppc_2_4_devel-2005-10-25-1440/include/scsi /usr/s
rc/linuxppc_2_4_devel-2005-10-25-1440/include/net
/usr/src/linuxppc_2_4_devel-2005-10-25-1440/includ
e/math-emu \( -name SCCS -o -name .svn \) -prune -o -follow -name \*.h !
-name modversions.h -print`
> .hdepend
scripts/mkdep: argument list too long
make: *** [dep-files] Error 2
Can someone help me understand where that comes from?
Does it have something to do with the fact that I work under WinXP + Cygwin?
No need to say that I am a newbie to the Linux world... help me, Wolfgang
:-)
Noe Serres
Midi Ingenierie
Toulouse (FR)
[-- Attachment #2: Type: text/html, Size: 1301 bytes --]
^ permalink raw reply
* Re: "argument list too long"
From: Wolfgang Denk @ 2006-01-03 14:17 UTC (permalink / raw)
To: Noé SERRES; +Cc: Linuxppc-embedded
In-Reply-To: <f8bc181b0601030606x3b29ee28q@mail.gmail.com>
In message <f8bc181b0601030606x3b29ee28q@mail.gmail.com> you wrote:
>
> After a few minutes of dependency creation, I get the following error
> "argument list too long":
>
> scripts/mkdep -- `find
> /usr/src/linuxppc_2_4_devel-2005-10-25-1440/include/asm
> /usr/src/linuxppc_2_4
> _devel-2005-10-25-1440/include/linux
> /usr/src/linuxppc_2_4_devel-2005-10-25-1440/include/scsi /usr/s
> rc/linuxppc_2_4_devel-2005-10-25-1440/include/net
> /usr/src/linuxppc_2_4_devel-2005-10-25-1440/includ
> e/math-emu \( -name SCCS -o -name .svn \) -prune -o -follow -name \*.h !
> -name modversions.h -print`
> > .hdepend
> scripts/mkdep: argument list too long
> make: *** [dep-files] Error 2
>
> Can someone help me understand where that comes from?
The error comes from the fact that the find command (the part in
`...` above) generates a long list of file names which exceeds some
buffer in your shell.
> Does it have something to do with the fact that I work under WinXP + Cygwin?
Yes.
> No need to say that I am a newbie to the Linux world... help me, Wolfgang
> :-)
I try. Find the statement in the Makefile and use xargs to avoid a
long argument list. Something like this might help:
--- Makefile.ORIG 2006-01-03 15:15:48.000000000 +0100
+++ Makefile 2006-01-03 15:16:55.000000000 +0100
@@ -503,7 +503,7 @@
ifdef CONFIG_MODVERSIONS
$(MAKE) update-modverfile
endif
- scripts/mkdep -- `find $(FINDHPATH) \( -name SCCS -o -name .svn \) -prune -o -follow -name \*.h ! -name modversions.h -print` > .hdepend
+ find $(FINDHPATH) \( -name SCCS -o -name .svn \) -prune -o -follow -name \*.h ! -name modversions.h -print | xargs scripts/mkdep -- > .hdepend
scripts/mkdep -- init/*.c > .depend
ifdef CONFIG_MODVERSIONS
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
The optimum committee has no members.
- Norman Augustine
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox