public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Philby John <pjohn@in.mvista.com>
To: Gopala Gottumukkala <ggottumu@Cernium.com>
Cc: davinci-linux-open-source@linux.davincidsp.com,
	linux-media@vger.kernel.org
Subject: RE: USB MAssage Storage drivers
Date: Wed, 16 Dec 2009 21:50:07 +0530	[thread overview]
Message-ID: <1260980407.4253.65.camel@localhost.localdomain> (raw)
In-Reply-To: <03A2FA9E0D3DC841992E682BF5287718016D3A53@lipwig.Cernium.local>

On Wed, 2009-12-16 at 10:53 -0500, Gopala Gottumukkala wrote:
> (gcc version 3.4.3 (MontaVista 3.4.3-25.0.104.0600975 2006-07-06)) #4
> PREEMPT Tue Dec 15 18:10:24 EST 2009
> CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
> CPU: VIVT data cache, VIVT instruction cache
> Machine: DaVinci DM644x EVM
> Memory policy: ECC disabled, Data cache writeback
> DaVinci dm6446 variant 0x0
> Built 1 zonelists in Zone order, mobility grouping on.  Total pages:
> 50800

And what good is this above boot log? The log that would be of interest
is the one generated the moment you connect a USB Pen drive. A
cat /proc/bus/usb/devices would also give you related information on the
connected device. Please take a look.

Regards,
Philby


  parent reply	other threads:[~2009-12-16 16:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-30 15:51 [PATCH 3/4 v11] TVP7002 driver for DM365 santiago.nunez
2009-12-15 20:49 ` Hans Verkuil
2009-12-15 23:46   ` USB MAssage Storage drivers Gopala Gottumukkala
2009-12-16  7:21     ` Philby John
2009-12-16 15:53       ` Gopala Gottumukkala
2009-12-16 16:03         ` Michael Trimarchi
2009-12-16 16:17           ` Gopala Gottumukkala
2009-12-16 16:15         ` Subbrathnam, Swaminathan
2009-12-16 16:20         ` Philby John [this message]
2009-12-16 16:20         ` Sergei Shtylyov

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=1260980407.4253.65.camel@localhost.localdomain \
    --to=pjohn@in.mvista.com \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=ggottumu@Cernium.com \
    --cc=linux-media@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