Messages in this thread | | | Date | Mon, 11 Aug 2003 14:02:20 -0700 | Subject | IrDA patches for 2.6.X, resend | From | Jean Tourrilhes <> |
| |
Hi,
I've just downloaded and tested 2.6.0-test3, and I was surprised to see that the IrDA patches I sent you are included. That's incredibly fast ;-) Unfortunately, it seems that 3 patches were lost in the process. One of them did no longer apply to -test3 (my fault), so I rediffed it. All tested on -test3.
Thanks !
Jean
--------------------------------------------------------------
[FEATURE] : Add a new feature to the IrDA stack [CORRECT] : Fix to have the correct/expected behaviour [CRITICA] : Fix potential kernel crash
ir260_ircomm_owner.diff : ~~~~~~~~~~~~~~~~~~~~~~~ <Patch from Andrey Borzenkov> o [CORRECT] Update module refcount in IrCOMM module
ir260_nsc_39x_fixes.diff : ~~~~~~~~~~~~~~~~~~~~~~~~ <Patch from Jan Frey> o [CORRECT] Make NSC 3839x probe and init *really* work The new 3839x code was totally broken. Won't affect code for 38108/38338 chips.
ir2603_vlsi-05.diff : ~~~~~~~~~~~~~~~~~~~ <Patch from Martin Diehl> * correct endianess conversion of hardware exposed fields * we need to check crc16 of rx frames in SIR-mode (hardware does this in MIR/FIR modes). Use irda_calc_crc16. * get rid of BUG'gers - having them in interrupt path isn't fun. * don't return NET_XMIT_DROP when we drop (dev_kfree_skb_any) frames. This value is meant to ask for retransmit so we would corrupt the skb slab. * locking review, corrections and improvements: particularly focus on speed setting and start_xmit paths, but also reducing time we are staying with interrupts disabled. * printk-cleanup: less/better syslog msgs, use IRDA_DEBUG and friends. * default qos_mtt_bits should be 1ms or longer (0x07), not exactly 1ms * rename IRENABLE_IREN -> IRENABLE_PHYANDCLOCK * few minor improvements * compatibility stuff to preserve 2.4 backport path * it's a pci controller, so we should depend on CONFIG_PCI * DRIVER_VERSION 0.5 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |