1. 18 2月, 2006 17 次提交
  2. 17 2月, 2006 4 次提交
    • D
      [PATCH] wireless/atmel: fix Open System authentication process bugs · 73451379
      Dan Williams 提交于
      This patch fixes a number of bugs in the authentication process:
      
      1) When falling back to Shared Key authentication mode from Open System,
      a missing 'return' would cause the auth request to be sent, but would
      drop the card into Management Error state.  When falling back, the
      driver should also indicate that it is switching to Shared Key mode by
      setting exclude_unencrypted.
      
      2) Initial authentication modes were apparently wrong in some cases,
      causing the driver to attempt Shared Key authentication mode when in
      fact the access point didn't support that mode or even had WEP disabled.
      The driver should set the correct initial authentication mode based on
      wep_is_on and exclude_unencrypted.
      
      3) Authentication response packets from the access point in Open System
      mode were getting ignored because the driver was expecting the sequence
      number of a Shared Key mode response.  The patch separates the OS and SK
      mode handling to provide the correct behavior.
      Signed-off-by: NDan Williams <dcbw@redhat.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      73451379
    • D
      [PATCH] wireless/atmel: fix setting TX key only in ENCODEEXT · 0d467502
      Dan Williams 提交于
      The previous patch that added ENCODEEXT and AUTH support to the atmel
      driver contained a slight error which would cause just setting the TX
      key index to also set the encryption key again.  This patch allows any
      combination of setting the TX key index and setting an encryption key.
      Signed-off-by: NDan Williams <dcbw@redhat.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      0d467502
    • F
      sis190: early setting of the pci driver private data · 10487fbd
      Francois Romieu 提交于
      Below this point, the error path will proceed through
      sis190_release_board(). It will happily oops if
      pci_set_drvdata() has not been issued.
      Signed-off-by: NFrancois Romieu <romieu@fr.zoreil.com>
      10487fbd
    • R
      [MMC] mmci: allow small data transfers · 0425a142
      Russell King 提交于
      If a data transfer is small (less than a FIFO size) we would
      hang waiting for the data to be read due to the PIO interrupt
      not occuring.  We allowed for this in our PIO interrupt handler,
      but not when setting up a data transfer.
      
      Apply the "fix" when setting up a data transfer as well.
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      0425a142
  3. 16 2月, 2006 3 次提交
    • A
      [PATCH] ide: touch softlockup detector during pio · 651c29a1
      Andrew Morton 提交于
      We're getting some softlockup false positives during heavy PIO operations.  So
      poke the lockup detector.
      
      Cc: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
      Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      651c29a1
    • C
      [PATCH] neofb: avoid resetting display config on unblank (v2) · 9f672004
      Christian Trefzer 提交于
      There were two mistakes in the register-read-on-(un)blank approach.
      
      - First, without proper register (un)locking the value read back will always
        be zero, and this is what I missed entirely until just now.  Due to this,
        the logic could not be verified at all and I tried some bogus checks which
        are completely stupid.
      
      - Second, the LCD status bit will always be set to zero when the backlight
        has been turned off.  Reading the value back during unblank will disable the
        LCD unconditionally, regardless of the state it is supposed to be in, since
        we set it to zero beforehand.
      
      So this is what we do now:
      
      - create a new variable in struct neofb_par, and use that to determine
        whether to read back registers (initialized to true)
      
      - before actually blanking the screen, read back the register to sense any
        possible change made through Fn key combo
      
      - use proper neoUnlock() / neoLock() to actually read something
      
      - every call to neofb_blank() determines if we read back next time: blanking
        disables readback, unblanking (FB_BLANK_UNBLANK) enables it
      
      This should give us a nice and clean state machine.  Has been thoroughly
      tested on a Dell Latitude CPiA / NM220 Chip docked to a C/Dock2 with attached
      CRT in all possible combinations of LCD/CRT on/off.  I changed the config via
      Fn key, let the console blank, unblanked by keypress - works flawlessly.
      Signed-off-by: NChristian Trefzer <ctrefzer@gmx.de>
      Cc: "Antonino A. Daplas" <adaplas@pol.net>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      9f672004
    • J
      [IA64] remove obsolete corporate address · d3454344
      Jes Sorensen 提交于
      Remove obsolete SGI address
      Signed-off-by: NJes Sorensen <jes@sgi.com>
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      d3454344
  4. 15 2月, 2006 16 次提交