public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: torvalds@osdl.org, Andrew Morton <akpm@osdl.org>
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: State of the Linux USB Subsystem for 2.6.18-rc6
Date: Sat, 9 Sep 2006 01:18:18 -0700	[thread overview]
Message-ID: <20060909081818.GA13055@kroah.com> (raw)

Here's a summary of the current state of the Linux USB subsystem, as of
2.6.18-rc6.

If the information in here is incorrect, or anyone knows of any
outstanding issues not listed here, please let me know.

List of outstanding regressions from 2.6.17:
	- none known.

List of outstanding regressions from older kernel versions:
	- none known.

There are a few outstanding patches waiting for Linus to pull from at:
	master.kernel.org:/pub/scm/linux/kernel/git/gregkh/usb-2.6.git/
as per a previous email message to him.

If interested, the list of all currently open USB bugs can be seen at:
    http://bugzilla.kernel.org/showdependencytree.cgi?id=5089&hide_resolved=1


Future patches that are currently in my quilt tree (as found at
	http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/
) for the USB subsystem are as follows.  All of these will be submitted
for inclusion into 2.6.19, except as noted:

	- USB core reworks to get suspend working better for the USB
	  core and drivers.
	- Initial framework for USB autosuspend (final patches enabling
	  this are not included as they caused problems on my machines,
	  they might be reworked and make it into 2.6.19 depending on
	  the issues involved).
	- OHCI changes to avoid root hub polling (this makes
	  dynamic-tick mechanisms work much better and takes USB off of
	  the list of the worse offenders of timer ticks in the kernel.)
	- helper functions for detecting usb endpoints instead of having
	  to remember those crazy bit fields all the time.  All drivers
	  are converted to use them, fixing a few bugs in the process.
	- some wireless USB infrastructure patches to make the future
	  wireless driver merge easier.
	- __must_check fixes to enable the whole USB subsystem to build
	  without compiler warnings anymore.
	- a number of new drivers:
		- aircable bluetoot dongle driver
		- adutux driver
		- vibrator driver
		- moschip 7840 usb-serial driver
		- moschip 7720 usb-serial driver (not ready for 2.6.19)
		- serqt usb-serial driver (not ready for 2.6.19)
	- ability to multi-thread the USB probe process.  Probably not
	  going to go into 2.6.19 as Alan Stern has come up with a
	  better way to do this.  I just need to integrate it into the
	  tree sometime in the near future.
	- other minor bugfixes that are not really critical or too big
	  to go into 2.6.18 at this period of time.

No new USB driver API changes are pending that I am aware of.


thanks,

greg k-h


                 reply	other threads:[~2006-09-09  8:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20060909081818.GA13055@kroah.com \
    --to=gregkh@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=torvalds@osdl.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