public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Okash Khawaja <okash.khawaja@gmail.com>
To: speakup@linux-speakup.org
Subject: Re: [patch 0/7] staging: speakup: migrate synths to use TTY-based comms
Date: Mon, 3 Apr 2017 22:02:47 +0100	[thread overview]
Message-ID: <20170403210247.GA4366@sanghar> (raw)
In-Reply-To: <20170403203925.GA1388@sanghar>

[-- Attachment #1: Type: text/plain, Size: 850 bytes --]

Patch correctly re-attached. Sorry about the trouble.

On Mon, Apr 03, 2017 at 09:39:25PM +0100, Okash Khawaja wrote:
> 
> 
> Hi,
> 
> The staging-next tree wasn't working for me, specially the usb modules.
> So I took following steps:
> 
> 1. Switch to kernel versio 4.10.0 (I guess others upto 4.10.8 will be
> fine)
> 
> 2. Copy drivers/staging/speakup directory from staging-next tree to
> overwrite the one in 4.10.0.
> 
> 3. Use the patch I have attached as the first patch instead of the one
> in this email series ([patch 1/7] staging: speakup: export
> tty_open_by_driver).
> 
> 4. Apply rest of the patches in this patchset.
> 
> That worked for me. As I have mentioned before, apollo and double talk
> lt worked fine but I haven't done thorough testing. If you have
> questions about applying patches, do let me know.
> 
> Thanks,
> Okash

[-- Attachment #2: 01_enable_kernel_access_to_tty_device --]
[-- Type: text/plain, Size: 2675 bytes --]

Index: linux-4.10.1/drivers/tty/tty_io.c
===================================================================
--- linux-4.10.1.orig/drivers/tty/tty_io.c
+++ linux-4.10.1/drivers/tty/tty_io.c
@@ -855,7 +855,7 @@
 
 int tty_hung_up_p(struct file *filp)
 {
-	return (filp->f_op == &hung_up_tty_fops);
+	return (filp && filp->f_op == &hung_up_tty_fops);
 }
 
 EXPORT_SYMBOL(tty_hung_up_p);
@@ -1368,7 +1368,10 @@
 	struct tty_struct *tty;
 
 	if (driver->ops->lookup)
-		tty = driver->ops->lookup(driver, file, idx);
+		if (!file)
+			tty = ERR_PTR(-EIO);
+		else
+			tty = driver->ops->lookup(driver, file, idx);
 	else
 		tty = driver->ttys[idx];
 
@@ -1986,7 +1989,7 @@
 		struct tty_driver *console_driver = console_device(index);
 		if (console_driver) {
 			driver = tty_driver_kref_get(console_driver);
-			if (driver) {
+			if (driver && filp) {
 				/* Don't let /dev/console block */
 				filp->f_flags |= O_NONBLOCK;
 				break;
@@ -2019,7 +2022,7 @@
  *	  - concurrent tty driver removal w/ lookup
  *	  - concurrent tty removal from driver table
  */
-static struct tty_struct *tty_open_by_driver(dev_t device, struct inode *inode,
+struct tty_struct *tty_open_by_driver(dev_t device, struct inode *inode,
 					     struct file *filp)
 {
 	struct tty_struct *tty;
@@ -2064,6 +2067,7 @@
 	tty_driver_kref_put(driver);
 	return tty;
 }
+EXPORT_SYMBOL(tty_open_by_driver);
 
 /**
  *	tty_open		-	open a tty device
Index: linux-4.10.1/drivers/tty/tty_port.c
===================================================================
--- linux-4.10.1.orig/drivers/tty/tty_port.c
+++ linux-4.10.1/drivers/tty/tty_port.c
@@ -335,7 +335,7 @@
  *	tty_port_block_til_ready	-	Waiting logic for tty open
  *	@port: the tty port being opened
  *	@tty: the tty device being bound
- *	@filp: the file pointer of the opener
+ *	@filp: the file pointer of the opener or NULL
  *
  *	Implement the core POSIX/SuS tty behaviour when opening a tty device.
  *	Handles:
@@ -369,7 +369,7 @@
 		tty_port_set_active(port, 1);
 		return 0;
 	}
-	if (filp->f_flags & O_NONBLOCK) {
+	if (filp ==  NULL || filp->f_flags & O_NONBLOCK) {
 		/* Indicate we are open */
 		if (C_BAUD(tty))
 			tty_port_raise_dtr_rts(port);
Index: linux-4.10.1/include/linux/tty.h
===================================================================
--- linux-4.10.1.orig/include/linux/tty.h
+++ linux-4.10.1/include/linux/tty.h
@@ -394,6 +394,8 @@
 /* tty_io.c */
 extern int __init tty_init(void);
 extern const char *tty_name(const struct tty_struct *tty);
+extern struct tty_struct *tty_open_by_driver(dev_t device, struct inode *inode,
+					     struct file *filp);
 #else
 static inline void console_init(void)
 { }

  reply	other threads:[~ UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Okash Khawaja
 ` [patch 1/7] tty: export tty_open_by_driver Okash Khawaja
   ` Samuel Thibault
 ` [patch 2/7] staging: speakup: add tty-based comms functions Okash Khawaja
   ` Samuel Thibault
 ` [patch 3/7] staging: speakup: migrate acntsa, bns, dummy and txprt to ttyio Okash Khawaja
   ` Samuel Thibault
 ` [patch 4/7] staging: speakup: add send_xchar and tiocmset methods Okash Khawaja
   ` Samuel Thibault
 ` [patch 5/7] staging: speakup: make input functionality swappable Okash Khawaja
   ` Samuel Thibault
 ` [patch 6/7] staging: speakup: add TTY-based input functionality Okash Khawaja
   ` Samuel Thibault
     ` Okash Khawaja
       ` Samuel Thibault
 ` [patch 7/7] staging: speakup: migrate apollo, ltlk, audptr, decext, dectlk and spkout Okash Khawaja
   ` Samuel Thibault
     ` Okash Khawaja
 ` [patch 0/7] staging: speakup: migrate synths to use TTY-based comms Okash Khawaja
   ` Okash Khawaja [this message]
 Okash Khawaja
 ` Samuel Thibault
   ` Okash Khawaja

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170403210247.GA4366@sanghar \
    --to=okash.khawaja@gmail.com \
    --cc=speakup@linux-speakup.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).