linux-kernel - [v4] New ldisc for WiLink7.0

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1269559223-4043-1-git-send-email-pavan_savoy@ti.com>
Date:	Thu, 25 Mar 2010 18:20:15 -0500
From:	pavan_savoy@...com
To:	marcel@...tmann.org, gregkh@...e.de, alan@...rguk.ukuu.org.uk
Cc:	linux-kernel@...r.kernel.org, pavan_savoy@...oo.co.in
Subject: [v4] New ldisc for WiLink7.0


Greg / Alan,


- moved to staging and completely self-contained
- REMOVed the sysfs entry creation at root and replaced it with
sending events via rfkill.
- verified and working with new logic
- patch re-ordered

Note:
Sorry for being annoying (some call it being persistent)

>Moved to staging directory as suggested.
>All the patches have been modified to now go into drivers/staging/

> Texas Instruments has introduced it's new series of WiLink chipsets
> which has Bluetooth, WLAN, FM-Rx and FM-Tx and GPS on 1 single chip.
> This series of chipsets allow apps processor to interface with the chip
> over a single UART mux-ed for all 3 (BT,FM and GPS) cores on chip and
> SDIO for WLAN.
> 
> The following list of patches introduces a new line discipline which allows 
> such muxing to happen, and 3 different BT, FM and GPS drivers would sit on
> top of this driver (registering/unregistering) and glue this to relevant s/w
> stacks.
> 
> This has been verified to work on TI's OMAP platforms(34xx,36xx and 44xx).

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/