Skip to content

cloud-kernel
cloud-kernel

bug2833 / cloud-kernel
与 Fork 源项目一致

Fork自 openanolis / cloud-kernel

通知 1
Star 0
Fork 0
cloud-kernel
cloud-kernel

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 11 10月, 2009 23 次提交
  3. 09 10月, 2009 1 次提交
  5. 07 10月, 2009 1 次提交
  7. 06 10月, 2009 2 次提交
  9. 05 10月, 2009 1 次提交
  11. 02 10月, 2009 3 次提交
  13. 01 10月, 2009 2 次提交
  15. 30 9月, 2009 1 次提交
  17. 29 9月, 2009 1 次提交
  19. 28 9月, 2009 5 次提交
    • T
      ALSA: hda - Enable MSI as default · 71623855
      由 Takashi Iwai 提交于 
      Since the recent kernel can handle MSI properly on non-Intel platforms,
let's enable MSI as default.

If any borken device is found, we can add the quirk entry to the list,
which is currently empty.
Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      71623855
    • T
      Merge branch 'fix/hda' into topic/hda · 08d7a253
      由 Takashi Iwai 提交于
      08d7a253
    • L
      Linux 2.6.32-rc1 · 17d857be
      由 Linus Torvalds 提交于
      17d857be
    • L
      alpha: Fix duplicate <asm/thread_info.h> include · b3b75cef
      由 Linus Torvalds 提交于 
      .. duplicated by merging the same fix twice, for details see commit
0d9df251 ("Merge
git://git.kernel.org/pub/scm/linux/kernel/git/sam/kbuild-fixes")
Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      b3b75cef
    • D
      tty: Fix regressions caused by commit b50989dc · f278a2f7
      由 Dave Young 提交于 
      The following commit made console open fails while booting:

	commit b50989dc
	Author: Alan Cox <alan@linux.intel.com>
	Date:   Sat Sep 19 13:13:22 2009 -0700

	tty: make the kref destructor occur asynchronously

Due to tty release routines run in a workqueue now, error like the
following will be reported while booting:

INIT open /dev/console Input/output error

It also causes hibernation regression to appear as reported at
http://bugzilla.kernel.org/show_bug.cgi?id=14229

The reason is that now there's latency issue with closing, but when
we open a "closing not finished" tty, -EIO will be returned.

Fix it as per the following Alan's suggestion:

  Fun but it's actually not a bug and the fix is wrong in itself as
  the port may be closing but not yet being destructed, in which case
  it seems to do the wrong thing.  Opening a tty that is closing (and
  could be closing for long periods) is supposed to return -EIO.

  I suspect a better way to deal with this and keep the old console
  timing is to split tty->shutdown into two functions.

  tty->shutdown() - called synchronously just before we dump the tty
  onto the waitqueue for destruction

  tty->cleanup() - called when the destructor runs.

  We would then do the shutdown part which can occur in IRQ context
  fine, before queueing the rest of the release (from tty->magic = 0
  ...  the end) to occur asynchronously

  The USB update in -next would then need a call like

       if (tty->cleanup)
               tty->cleanup(tty);

  at the top of the async function and the USB shutdown to be split
  between shutdown and cleanup as the USB resource cleanup and final
  tidy cannot occur synchronously as it needs to sleep.

  In other words the logic becomes

       final kref put
               make object unfindable

       async
               clean it up
Signed-off-by: NDave Young <hidave.darkstar@gmail.com>
[ rjw: Rebased on top of 2.6.31-git, reworked the changelog. ]
Signed-off-by: N"Rafael J. Wysocki" <rjw@sisk.pl>
[ Changed serial naming to match new rules, dropped tty_shutdown as per
  comments from Alan Stern  - Linus ]
Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      f278a2f7