mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Helge Hafting" <helge.hafting@aitel.hist.no>
Cc: "Helge Hafting" <helgehaf@aitel.hist.no>,
	linux-kernel@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net
Subject: Re: usb touchscreen breakage in 2.6.21-rc5-mm4 ?
Date: Tue, 10 Apr 2007 11:39:21 -0400	[thread overview]
Message-ID: <d120d5000704100839s47d07ff1gc47ce9ea97d54002@mail.gmail.com> (raw)
In-Reply-To: <461B9DFF.9080704@aitel.hist.no>

On 4/10/07, Helge Hafting <helge.hafting@aitel.hist.no> wrote:
> Dmitry Torokhov wrote:
> > Hmm, I am concerned because not only you don't have an input device created,
> > you don't even see the driver being registered with usbcore. Could you please
> > try booting with debug_initcall to see with what error code usbtouchscreen
> > initialization fails?
> >
> Here is the dmesg from a boot with debug_initcall.
> I can't see any messages from usbtouchscreen.
> For me, it looks like the touchscreen is discovered and then
> nothing happens to it.
>

*sigh* When will I learn to spell names of kernel parameters
correctly? It is initcall_debug, not debug_initcall :( Could you try
again, please?

-- 
Dmitry

  reply	other threads:[~2007-04-10 15:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-07  0:54 Helge Hafting
2007-04-07  2:37 ` Dmitry Torokhov
2007-04-09 22:36   ` Helge Hafting
2007-04-10  1:06     ` Andrew Morton
2007-04-10 15:25       ` Helge Hafting
2007-04-10  2:30     ` Dmitry Torokhov
2007-04-10 14:23       ` Helge Hafting
2007-04-10 15:39         ` Dmitry Torokhov [this message]
2007-04-11  9:50           ` Helge Hafting
2007-04-11 14:37             ` Dmitry Torokhov
2007-04-12 18:52               ` Helge Hafting

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=d120d5000704100839s47d07ff1gc47ce9ea97d54002@mail.gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=helge.hafting@aitel.hist.no \
    --cc=helgehaf@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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®