[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <op.vf4vrwa67p4s8u@pikus>
Date: Tue, 20 Jul 2010 10:41:46 +0200
From: Michał Nazarewicz <m.nazarewicz@...sung.com>
To: Alan Stern <stern@...land.harvard.edu>,
David Brownell <david-b@...bell.net>
Cc: Greg KH <greg@...ah.com>,
Kyungmin Park <kyungmin.park@...sung.com>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Kernel development list <linux-kernel@...r.kernel.org>,
Dries Van Puymbroeck <Dries.VanPuymbroeck@...imo.com>
Subject: Re: [PATCHv3 1/3] USB: gadget: mass/file storage: set serial number
On Mon, 19 Jul 2010 19:41:10 +0200, David Brownell <david-b@...bell.net> wrote:
>> I'm not entirely sure of what the issue with
>> the patches is really. It merely adds a serial
>> number to the gadgets using MSF and that's all.
>
> Go back and read what I wrote then. The issue is
> that THERE ALREADY IS SUCH A MECHANISM. We neither
> need or want another way to do it. The answer is to
> use the existing mechanism correctly.
There is no existing mechanism. If the module does not set the
iSerialNumber field the iSerialNumber module parameter won't work
and I don't see any other way to set the string. If there is one,
please show it to me.
> Plus, you seem to be overlooking the basic need
> (for userspace) to manage these IDs so they're
> properly unique. Two gadgets should never end up
> using the same serial number.
I'm not overlooking that. I simply consider that a separate issue.
Driver should provide some kind of default (just like File Storage
Gadget) and the fact that user space should override it is another
matter in my opinion.
This is especially true, since the iSerialNumber module parameter
won't work without iSerialNumber set (which I pointed several
times).
--
Best regards, _ _
| Humble Liege of Serenely Enlightened Majesty of o' \,=./ `o
| Computer Science, Michał "mina86" Nazarewicz (o o)
+----[mina86*mina86.com]---[mina86*jabber.org]----ooO--(_)--Ooo--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists