| 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
| ||
|
Message-Id: <1280301960-16474-2-git-send-email-pavan_savoy@ti.com> Date: Wed, 28 Jul 2010 02:26:00 -0500 From: pavan_savoy@...com To: gregkh@...e.de, alan@...rguk.ukuu.org.uk Cc: devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org, pavan_savoy@...y.com, Pavan Savoy <pavan_savoy@...com> Subject: [PATCH 2/2] drivers:staging:ti-st: update ABI and TODO From: Pavan Savoy <pavan_savoy@...com> update TODO to reflect the items taken care of, update ABI to reflect the new debugfs entries exposed. Signed-off-by: Pavan Savoy <pavan_savoy@...com> --- drivers/staging/ti-st/TODO | 10 +++------- drivers/staging/ti-st/sysfs-uim | 12 ++++++++++++ 2 files changed, 15 insertions(+), 7 deletions(-) diff --git a/drivers/staging/ti-st/TODO b/drivers/staging/ti-st/TODO index 3f68ea1..6a105ed 100644 --- a/drivers/staging/ti-st/TODO +++ b/drivers/staging/ti-st/TODO @@ -11,16 +11,12 @@ a st_register() would know whether the registration from BT/FM or GPS was intend 2. Improve upon the way requirement of line discipline is communicated to user-space, The current user-space application which open/installs ldisc as and when required can be found at, -http://git.omapzoom.org/?p˙atform/hardware/ti/omap3.git;a˙ob;f˙_st/uim/uim.c;h.a16c2c2b5085eb54a1bbc7096d779d7594eb11;hbělair +http://dev.omapzoom.org/pub/scm/jsistla/L23-btfm.git +branch: UIM 3. Re-view/Re-work on the locking. -4. Re-structure to make the ldisc driver more generic for chipsets which mux -multiple connectivity (BT, FM, GPS) upon 1 TTY port. - -5. Remove global references by providing a context which can be moved around the driver like the other ldisc drivers. (ldiscs tend to use tty's disc_data and platform devices use the device's driver data) - -6. Step up and maintain this driver to ensure that it continues +4. Step up and maintain this driver to ensure that it continues to work. Having the hardware for this is pretty much a requirement. If this does not happen, the will be removed in the 2.6.35 kernel release. diff --git a/drivers/staging/ti-st/sysfs-uim b/drivers/staging/ti-st/sysfs-uim index 10311af..626bda5 100644 --- a/drivers/staging/ti-st/sysfs-uim +++ b/drivers/staging/ti-st/sysfs-uim @@ -14,3 +14,15 @@ Description: uninstallation would be ppolling on this device and listening on events which would suggest either to install or un-install line discipline + +What: /sys/kernel/debug/ti-st/version +Contact: Pavan Savoy <pavan_savoy@...com> +Description: + WiLink chip's ROM version exposed to user-space for some + proprietary protocol stacks to make use of. + +What: /sys/kernel/debug/ti-st/protocols +Contact: Pavan Savoy <pavan_savoy@...com> +Description: + The reason for chip being ON, the list of protocols registered. + -- 1.5.6.3 -- 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/
Powered by blists - more mailing lists