From: Sascha Hauer <s.hauer@pengutronix.de>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: Update/include some functions from the Kernel
Date: Thu, 17 Jul 2014 14:41:51 +0200 [thread overview]
Message-ID: <20140717124151.GJ23235@pengutronix.de> (raw)
In-Reply-To: <53C79763.7050406@gmail.com>
On Thu, Jul 17, 2014 at 11:29:07AM +0200, Sebastian Hesselbarth wrote:
> On 07/17/2014 07:33 AM, Sascha Hauer wrote:
> >On Thu, Jul 17, 2014 at 01:15:33AM +0200, Sebastian Hesselbarth wrote:
> >>On 07/15/2014 03:49 PM, Sascha Hauer wrote:
> >>>This adds/updates some lowlevel bitmap/bitop stuff from the
> >>>Kernel. Needed by upcoming USB updates.
> >>
> >>Sascha,
> >>
> >>just curious what "USB updates" there are?
> >
> >The updates are only USB core related, like turning the hub driver into
> >a device and make fix up the USB device hierarchy. The other stuff is
> >USB gadget specific: Update to v3.15 and composite gadget support
>
> Ok, for the xHCI driver, I am about to bring up the ports. But AFAKT,
> it will be basically fine to reuse the EHCI hub code. The way data is
> sent later, is different from EHCI. I still have to dig into both xHCI
> and EHCI code and specs to be sure about it.
>
> BTW, if USB2.0 is a reasonable fallback for both, xHCI devices and HC,
> I guess it should be fine to just support the 2.0 stuff.
>
> Up to now, I already stumbled upon some legacy stuff (from u-boot?),
> e.g. USB_SPEED defines vs enum, struct usb_{config,interface}_descriptor
> collusion.
I have patches for these issues already in my series. I'll post it soon.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2014-07-17 12:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 13:49 Sascha Hauer
2014-07-15 13:49 ` [PATCH 1/5] include: Add DECLARE_BITMAP from kernel Sascha Hauer
2014-07-15 13:49 ` [PATCH 2/5] include: Add round_up/round_down macros " Sascha Hauer
2014-07-15 13:49 ` [PATCH 3/5] include: Add foreign endianess adding functions " Sascha Hauer
2014-07-15 13:49 ` [PATCH 4/5] lib: Add bitmap " Sascha Hauer
2014-07-15 13:49 ` [PATCH 5/5] include: update bitop " Sascha Hauer
2014-07-15 18:42 ` Update/include some functions from the Kernel Antony Pavlov
2014-07-16 8:27 ` Sascha Hauer
2014-07-16 23:15 ` Sebastian Hesselbarth
2014-07-17 5:33 ` Sascha Hauer
2014-07-17 9:29 ` Sebastian Hesselbarth
2014-07-17 12:41 ` Sascha Hauer [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=20140717124151.GJ23235@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=sebastian.hesselbarth@gmail.com \
/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