All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tasslehoff <tasskjapp@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Proposed patch for usb-gadget
Date: Wed, 18 Nov 2009 10:56:43 +0100	[thread overview]
Message-ID: <4B03C4DB.2020105@gmail.com> (raw)
In-Reply-To: <1258537737.25369.684.camel@lenovo.internal.reciva.com>

The only reason I did this was because setup_usb() doesn't use the 
argument at all, but uses $MODULE_OPTIONS directly.

Another fix is:

-               modprobe "$1" "$MODULE_OPTIONS"
+               modprobe $1 $2

and then remove quotes around all occurences of $MODULE_OPTIONS, but I 
like the first one better :)

- Tasslehoff


On 11/18/2009 10:48 AM, Phil Blundell wrote:
> On Wed, 2009-11-18 at 10:42 +0100, Tasslehoff Kjappfot wrote:
>    
>> usb-gadget failed when MODULE_OPTIONS contained more than one option. Here's
>> the patch I used to make it work.
>>      
> Thanks for the patch.  However, it seems to do two different things:
>
> -               modprobe "$1" "$MODULE_OPTIONS"
> +               modprobe "$1" $MODULE_OPTIONS
>
> I understand this bit, and it does seem reasonable since MODULE_OPTIONS
> might, as you say, contain multiple strings.
>
> -       networking)     setup_usb g_ether "$MODULE_OPTIONS" ;;
> -       zero)           setup_usb g_zero "$MODULE_OPTIONS" ;;
> -       midi)           setup_usb g_midi "$MODULE_OPTIONS" ;;
> -       printer)        setup_usb g_printer "$MODULE_OPTIONS" ;;
> -       gadgetfs)       setup_usb gadgetfs "$MODULE_OPTIONS" ;;
> -       composite)      setup_usb g_cdc "$MODULE_OPTIONS" ;;
> -       serial)         setup_usb g_serial "$MODULE_OPTIONS" ;;
> -       storage)        setup_usb g_file_storage "$MODULE_OPTIONS" ;;
> +       networking)     setup_usb g_ether ;;
> +       zero)           setup_usb g_zero ;;
> +       midi)           setup_usb g_midi ;;
> +       printer)        setup_usb g_printer ;;
> +       gadgetfs)       setup_usb gadgetfs ;;
> +       composite)      setup_usb g_cdc ;;
> +       serial)         setup_usb g_serial ;;
>
> But this part seems a bit strange.  Can you expand on why this is
> necessary and/or desirable?
>
> p.
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>    




  reply	other threads:[~2009-11-18  9:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-18  9:42 Proposed patch for usb-gadget Tasslehoff Kjappfot
2009-11-18  9:48 ` Phil Blundell
2009-11-18  9:56   ` Tasslehoff [this message]
2009-11-18 10:22     ` Phil Blundell
2010-02-16  8:06       ` Stefan Schmidt

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=4B03C4DB.2020105@gmail.com \
    --to=tasskjapp@gmail.com \
    --cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.