From: Bryan O'Donoghue <bodonoghue@codehermit.ie>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] USB device configuration
Date: Wed, 9 May 2007 22:43:27 +0100 [thread overview]
Message-ID: <20070509224327.41b3935a@localhost.localdomain> (raw)
In-Reply-To: <20070509091930.GD11070@enneenne.com>
On Wed, 9 May 2007 11:19:31 +0200
Rodolfo Giometti <giometti@enneenne.com> wrote:
> I think that the correct sequence into usbtty should be:
>
> @@ -554,11 +554,11 @@ int drv_usbtty_init (void)
> usbtty_init_strings ();
> usbtty_init_instances ();
>
> + usbtty_init_endpoints ();
> +
> udc_startup_events (device_instance);/* Enable dev, init
> udc pointers */ udc_connect (); /* Enable pullup for host
> detection */
> - usbtty_init_endpoints ();
> -
> /* Device initialization */
> memset (&usbttydev, 0, sizeof (usbttydev));
>
> Comments?
Greetings Rodolfo.
Apologies, for the late response, sometimes I work/sleep without
checking my home mail and missed this for ~ 48 hours.
Umm, *provisionally* this appears not to be a problem for
usbdcore_mpc8xx.c... just having a quick scan of usbdcore_omap1510 I
don't immediately see a way that code could be broken by such a
change... *then again* keep in mind when I was mucking with the
usbtty stuff, I specifically tried *not* to change the order that
things happen in, for fear of breaking other people's - omap stuff.
Perhaps someone using the omap1510 in USB device mode would be in a
better position to make a statement on that.
In this specific instance though we _should_ be safe enough. Even
still when you submit your modifications to the list, I'll ensure I
do a test run from the POV of usbdcore_mpc8xx, just to make sure your
code doesn't break my code !
Best,
Bryan
prev parent reply other threads:[~2007-05-09 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 9:03 [U-Boot-Users] USB device configuration Rodolfo Giometti
2007-05-09 9:19 ` Rodolfo Giometti
2007-05-09 21:43 ` Bryan O'Donoghue [this message]
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=20070509224327.41b3935a@localhost.localdomain \
--to=bodonoghue@codehermit.ie \
--cc=u-boot@lists.denx.de \
/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