Hello Dan,
Dan Nicholson [2009-05-10 8:17 -0700]:
> Martin, I noticed a couple minor build tweaks. You committed something
> to check for gperf in configure.ac, but then you never use $(GPERF) in
> keymap/Makefile.am.
Good point, fixed (950cea7adef72497d39de0c71b8ef943b093125b)
> On the same no
On Sat, May 9, 2009 at 3:39 AM, Martin Pitt wrote:
> Martin Pitt [2009-05-08 15:28 +0200]:
>> As discussed, it is done now, including conversion of all of
>> hal-info's current keymaps. I created my own udev-extra branch for
>> that, since I'm still waiting for a git.kernel.org account.
>
> I got
On Sat, May 9, 2009 at 12:39, Martin Pitt wrote:
> I committed my stuff to udev-extras trunk now.
Looks good. Thanks for doing this.
> I don't see it on
> http://git.kernel.org/?p=linux/hotplug/udev-extras.git;a=summary yet,
> but I do see it in "git log" on master.k.o. I guess there's some
> c
Martin Pitt [2009-05-08 15:28 +0200]:
> As discussed, it is done now, including conversion of all of
> hal-info's current keymaps. I created my own udev-extra branch for
> that, since I'm still waiting for a git.kernel.org account.
I got my account. I also got a lot of positive and no negative tes
Hello again,
CC'ing hal@ to let people know who don't hang out on devkit-devel@
yet. Please see [1] for the complete thread.
Martin Pitt [2009-05-05 13:21 +0200]:
> I got quite the hang of adding model specific keymaps to hal-info
> these days, and I wondered what the replacement of hal-setup-key
On Thu, May 7, 2009 at 15:58, Martin Pitt wrote:
> Kay Sievers [2009-05-07 13:50 +0200]:
>> Only if you do ="[Cc][Aa][Ss][Ee]". :)
>
> Oh, *headdesk*, indeed. Since I'm generating them mostly
> automatically, that shouldn't be a problem. Looks weird, but works.
Hehe, good.
> Would it be too evi
Hello Kay,
Kay Sievers [2009-05-07 13:50 +0200]:
> > Ah, another thing is "contains_ncase". I don't think udev rules can do
> > case insensitive string matching, can they?
>
> Only if you do ="[Cc][Aa][Ss][Ee]". :)
Oh, *headdesk*, indeed. Since I'm generating them mostly
automatically, that shou
On Thu, May 7, 2009 at 09:08, Martin Pitt wrote:
> Kay Sievers [2009-05-06 1:16 +0200]:
>> > Originally I intended this to become a script which we can run
>> > permanently to maintain keymaps in hal-info side by side with the new
>> > udev-extras rules. However, udev rules are not expressive eno
On Thu, May 7, 2009 at 13:00, Martin Pitt wrote:
> Kay Sievers [2009-05-07 12:29 +0200]:
>> > Done. I put the keymaps themselves into /lib/udev/keymaps/ for now
>> > (instead of /usr/share/udev/keymaps/, as in my first sketch).
>>
>> Ah, i see. What's the reason for that? Not that I have objection
Kay Sievers [2009-05-07 12:29 +0200]:
> > Done. I put the keymaps themselves into /lib/udev/keymaps/ for now
> > (instead of /usr/share/udev/keymaps/, as in my first sketch).
>
> Ah, i see. What's the reason for that? Not that I have objections to
> do that.
The keyboard should usually be detecte
On Thu, May 7, 2009 at 11:58, Martin Pitt wrote:
> Kay Sievers [2009-05-06 1:16 +0200]:
>> > - Would you prefer using input-utils or a copy of the input-kbd
>> > script in udev-extras?
>>
>> I think, we should put all of that, including the binary, in a subdir
>> in udev-extras, and install th
Kay Sievers [2009-05-06 1:16 +0200]:
> > - Would you prefer using input-utils or a copy of the input-kbd
> > script in udev-extras?
>
> I think, we should put all of that, including the binary, in a subdir
> in udev-extras, and install the binary in /lib/udev/. Then we are free
> to change stu
Kay Sievers [2009-05-06 1:16 +0200]:
> > Originally I intended this to become a script which we can run
> > permanently to maintain keymaps in hal-info side by side with the new
> > udev-extras rules. However, udev rules are not expressive enough for
> > some of the weirder constructs we currently
Hello Kay,
Kay Sievers [2009-05-06 1:16 +0200]:
> > Originally I intended this to become a script which we can run
> > permanently to maintain keymaps in hal-info side by side with the new
> > udev-extras rules. However, udev rules are not expressive enough for
> > some of the weirder constructs
On Tue, May 5, 2009 at 23:09, Martin Pitt wrote:
> I now wrote a small hackish script (current version: [1]) which
> convers a set of keymap fdi files into udev rules:
Cool.
> Originally I intended this to become a script which we can run
> permanently to maintain keymaps in hal-info side by si
Hello Kay,
Kay Sievers [2009-05-05 13:48 +0200]:
> "[dmi/id]:" should work to get to that information.
That's it, thanks!
> I think Lennart had some tool too, that may be useful, if I remember
> correctly.
We discussed keyfuzz in #udev today. However, most of it is not
necessary any more, and
On Tue, May 5, 2009 at 13:21, Martin Pitt wrote:
> I got quite the hang of adding model specific keymaps to hal-info
> these days, and I wondered what the replacement of hal-setup-keymap
> will be in the new udev/DK world?
>
> I didn't find any existing discussion about this. Is someone already
>
Hello all,
I got quite the hang of adding model specific keymaps to hal-info
these days, and I wondered what the replacement of hal-setup-keymap
will be in the new udev/DK world?
I didn't find any existing discussion about this. Is someone already
working on this? If not, I'd be quite interested
18 matches
Mail list logo
