tags 381952 + patch
thanks
On Tue, Aug 08, 2006 at 01:19:32AM +0200, Steinar H. Gunderson wrote:
Autodetecting a Latitude is not difficult, but rather hairy -- it's
basically a matter of
dmidecode --string system-product-name | grep -q '^Latitude '
LATITUDE=yes
I've written up a quick
+Dell*)
+ case $name in
+ Latitude*)
+MODEL=latitude
+;;
+ esac
+ ;;
Well, on my Dell X1, the following *breaks* the support for volume
control keys:
Section InputDevice
Identifier Generic Keyboard
Driver keyboard
On Tue, Aug 08, 2006 at 07:31:24AM -0500, Christian Perrier wrote:
Well, on my Dell X1, the following *breaks* the support for volume
control keys:
This is precisely the kind of data we need to pull in. Two valuable points:
1. I missed the inspiron keymap altogether, probably since it didn't
On Tue, Aug 08, 2006 at 02:43:51PM +0200, Steinar H. Gunderson wrote:
2. There should be an exception for X1. Do you have the dmidecode data
handy?
On second thought (as discussed on IRC), you're probably running into #381882
here, so no exception should be needed (just a bugfix).
/*
Package: xserver-xorg
Version: 1:7.0.22
Severity: wishlist
Dell Latitudes have a specific XKB model (latitude) which is useful
for detecting certain extra keys, such as the volume keys. However, this
is not autodetected by the xserver-xorg configuration script, so the
user has to enable that
5 matches
Mail list logo
