From: Salvatore Iovene <salvatore.iovene@googlemail.com>
To: Frans Pop <elendil@planet.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: /lib/modules/2.6.31-10/build/drivers/input/hid-ids.h - where is it?
Date: Mon, 14 Sep 2009 15:46:10 +0300 [thread overview]
Message-ID: <c64207c00909140546v691d17f5sfc94bf425307e037@mail.gmail.com> (raw)
In-Reply-To: <200909141438.11560.elendil@planet.nl>
On Mon, Sep 14, 2009 at 3:38 PM, Frans Pop <elendil@planet.nl> wrote:
>> I have upgraded to Ubuntu 9.10 yesterday, and that brought in the
>> 2.6.31-10 kernel. I always build the linuxwacom drivers myself, and
>> they use the file in the subject (not 100% sure about the path,
>> though: I recalled it from memory).
>> Despite having all the dependencies that allowed me to build
>> linuxwacom in the past, now that file is missing.
>
> Note that when you build out-of-tree drivers you will never be guaranteed
> that your driver source will continue to build with a new kernel. When
> things break and you cannot solve the problem yourself, you should
> normally contact the organization or person where you got the driver, not
> the kernel community.
Hi, and thanks for your reply. I asked here because I thought
something might have changed into the kernel that broke linuxwacom and
they didn't know yet.
> AFAICT in this case the file was simply moved to:
> drivers/hid/hid-ids.h
> ^^^
Actually, that's the place where the file is looked for, despite the
mistake in the subject of my email (I said I recalled from memory :))
See line 38 at http://linuxwacom.cvs.sourceforge.net/viewvc/linuxwacom/linuxwacom-dev/src/2.6.31/Makefile.in?revision=1.1&view=markup
So the question remains: why don't I have that file?
Thanks!
--
Salvatore Iovene
http://www.iovene.com/
http://www.geekherocomic.com/
next prev parent reply other threads:[~2009-09-14 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 11:34 Salvatore Iovene
2009-09-14 12:38 ` Frans Pop
2009-09-14 12:46 ` Salvatore Iovene [this message]
2009-09-14 12:50 ` Jiri Kosina
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c64207c00909140546v691d17f5sfc94bf425307e037@mail.gmail.com \
--to=salvatore.iovene@googlemail.com \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®