Re: [HELP REQUESTED from the community] Was: Staging status of speakup
On Wed, Sep 18, 2019 at 08:16:42AM +0200, Greg Kroah-Hartman wrote: > On Tue, Sep 17, 2019 at 06:03:53PM -0700, Gregory Nowak wrote: > > On Tue, Sep 17, 2019 at 10:01:18AM +0200, Greg Kroah-Hartman wrote: > > > On Mon, Sep 16, 2019 at 03:38:48PM -0700, Gregory Nowak wrote: > > > > On Mon, Sep 16, 2019 at 04:11:00PM +0200, Greg Kroah-Hartman wrote: > > > > > On Mon, Sep 16, 2019 at 03:47:28PM +0200, Samuel Thibault wrote: > > > > > > Okash Khawaja, le dim. 15 sept. 2019 19:41:30 +0100, a ecrit: > > > > > > > I have attached the descriptions. > > > > > > > > > > > > Attachment is missing :) > > > > > > > > > > I saw it :) > > > > > > > > > > Anyway, please put the Description: lines without a blank after that, > > > > > with the description text starting on that same line. > > > > > > > > > > thanks! > > > > > > > > > > greg k-h > > > > > > > > It's attached. Hope the indentation is OK. > > > > > > Alignment is a bit off, you forgot a tab after "Description:" > > > > > > And you have some trailing whitespace in the document :( > > > > > > thanks, > > > > > > greg k-h > > > > > > > I put in the tabs after "Description:" and did the best I could to fix > > the alignment, and to find and get rid of the white space. If the > > alignment is still off, or if there is still white space I missed, > > could someone else please correct that? Thanks. > > Extra line between each attribute (before the "What:" line) would be > nice. In a previous post above, you wrote: On Mon, Sep 16, 2019 at 04:11:00PM +0200, Greg Kroah-Hartman wrote: > Anyway, please put the Description: lines without a blank after that, > with the description text starting on that same line. I understood that to mean that the description text should start on the same line, and the blank lines after the description text should be removed. I've put them back in. Someone more familiar with the speakup code will have to dig into it to resolve the TODO items I suppose. On Wed, Sep 18, 2019 at 03:28:05PM +0200, Didier Spaier wrote: > Trailing white spaces removed in attachment. > Alignment LGTM. Thank you. This is the copy I put the blank lines into, and am attaching with the original file name. Greg N -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org What: /sys/accessibility/speakup/attrib_bleep KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:Beeps the PC speaker when there is an attribute change such as foreground or background color when using speakup review commands. One = on, zero = off. What: /sys/accessibility/speakup/bell_pos KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:This works much like a typewriter bell. If for example 72 is echoed to bell_pos, it will beep the PC speaker when typing on a line past character 72. What: /sys/accessibility/speakup/bleeps KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:This controls whether one hears beeps through the PC speaker when using speakup's review commands. TODO: what values does it accept? What: /sys/accessibility/speakup/bleep_time KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:This controls the duration of the PC speaker beeps speakup produces. TODO: What are the units? Jiffies? What: /sys/accessibility/speakup/cursor_time KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:This controls cursor delay when using arrow keys. When a connection is very slow, with the default setting, when moving with the arrows, or backspacing etc. speakup says the incorrect characters. Set this to a higher value to adjust for the delay and better synchronisation between cursor position and speech. What: /sys/accessibility/speakup/delimiters KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:Delimit a word from speakup. TODO: add more info What: /sys/accessibility/speakup/ex_num KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:TODO:
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
On Tue, Sep 17, 2019 at 10:01:18AM +0200, Greg Kroah-Hartman wrote: > On Mon, Sep 16, 2019 at 03:38:48PM -0700, Gregory Nowak wrote: > > On Mon, Sep 16, 2019 at 04:11:00PM +0200, Greg Kroah-Hartman wrote: > > > On Mon, Sep 16, 2019 at 03:47:28PM +0200, Samuel Thibault wrote: > > > > Okash Khawaja, le dim. 15 sept. 2019 19:41:30 +0100, a ecrit: > > > > > I have attached the descriptions. > > > > > > > > Attachment is missing :) > > > > > > I saw it :) > > > > > > Anyway, please put the Description: lines without a blank after that, > > > with the description text starting on that same line. > > > > > > thanks! > > > > > > greg k-h > > > > It's attached. Hope the indentation is OK. > > Alignment is a bit off, you forgot a tab after "Description:" > > And you have some trailing whitespace in the document :( > > thanks, > > greg k-h > I put in the tabs after "Description:" and did the best I could to fix the alignment, and to find and get rid of the white space. If the alignment is still off, or if there is still white space I missed, could someone else please correct that? Thanks. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org What: /sys/accessibility/speakup/attrib_bleep KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:Beeps the PC speaker when there is an attribute change such as foreground or background color when using speakup review commands. One = on, zero = off. What: /sys/accessibility/speakup/bell_pos KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:This works much like a typewriter bell. If for example 72 is echoed to bell_pos, it will beep the PC speaker when typing on a line past character 72. What: /sys/accessibility/speakup/bleeps KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:This controls whether one hears beeps through the PC speaker when using speakup's review commands. TODO: what values does it accept? What: /sys/accessibility/speakup/bleep_time KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:This controls the duration of the PC speaker beeps speakup produces. TODO: What are the units? Jiffies? What: /sys/accessibility/speakup/cursor_time KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:This controls cursor delay when using arrow keys. When a connection is very slow, with the default setting, when moving with the arrows, or backspacing etc. speakup says the incorrect characters. Set this to a higher value to adjust for the delay and better synchronisation between cursor position and speech. What: /sys/accessibility/speakup/delimiters KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:Delimit a word from speakup. TODO: add more info What: /sys/accessibility/speakup/ex_num KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:TODO: What: /sys/accessibility/speakup/key_echo KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:Controls if speakup speaks keys when they are typed. One = on, zero = off or don't echo keys. What: /sys/accessibility/speakup/keymap KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:Speakup keymap remaps keys to Speakup functions. It uses a binary format. A special program called genmap is needed to compile a textual keymap into the binary format which is then loaded into /sys/accessibility/speakup/keymap. What: /sys/accessibility/speakup/no_interrupt KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:Controls if typing interrupts output from speakup. With no_interrupt set to zero, typing on the keyboard will interrupt speakup if for example the say screen command is used before the entire screen is read. With no_interrupt set to one, if the say screen command is used, and one then types on the keyboard, speakup will continue to say the whole screen regardless until it finishes. What: /sys/acces
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
On Mon, Sep 16, 2019 at 04:11:00PM +0200, Greg Kroah-Hartman wrote: > On Mon, Sep 16, 2019 at 03:47:28PM +0200, Samuel Thibault wrote: > > Okash Khawaja, le dim. 15 sept. 2019 19:41:30 +0100, a ecrit: > > > I have attached the descriptions. > > > > Attachment is missing :) > > I saw it :) > > Anyway, please put the Description: lines without a blank after that, > with the description text starting on that same line. > > thanks! > > greg k-h It's attached. Hope the indentation is OK. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org What: /sys/accessibility/speakup/attrib_bleep KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: Beeps the PC speaker when there is an attribute change such as foreground or background color when using speakup review commands. One = on, zero = off. What: /sys/accessibility/speakup/bell_pos KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: This works much like a typewriter bell. If for example 72 is echoed to bell_pos, it will beep the PC speaker when typing on a line past character 72. What: /sys/accessibility/speakup/bleeps KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: This controls whether one hears beeps through the PC speaker when using speakup's review commands. TODO: what values does it accept? What: /sys/accessibility/speakup/bleep_time KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: This controls the duration of the PC speaker beeps speakup produces. TODO: What are the units? Jiffies? What: /sys/accessibility/speakup/cursor_time KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: This controls cursor delay when using arrow keys. When a connection is very slow, with the default setting, when moving with the arrows, or backspacing etc. speakup says the incorrect characters. Set this to a higher value to adjust for the delay and better synchronisation between cursor position and speech. What: /sys/accessibility/speakup/delimiters KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: Delimit a word from speakup. TODO: add more info What: /sys/accessibility/speakup/ex_num KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: TODO: What: /sys/accessibility/speakup/key_echo KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: Controls if speakup speaks keys when they are typed. One = on, zero = off or don't echo keys. What: /sys/accessibility/speakup/keymap KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: Speakup keymap remaps keys to Speakup functins. It uses a binary format. A special program called genmap is needed to compile a textual keymap into the binary format which is then loaded into /sys/accessibility/speakup/keymap. What: /sys/accessibility/speakup/no_interrupt KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: Controls if typing interrupts output from speakup. With no_interrupt set to zero, typing on the keyboard will interrupt speakup if for example the say screen command is used before the entire screen is read. With no_interrupt set to one, if the say screen command is used, and one then types on the keyboard, speakup will continue to say the whole screen regardless until it finishes. What: /sys/accessibility/speakup/punc_all KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: This is a list of all the punctuation speakup should speak when punc_level is set to four. What: /sys/accessibility/speakup/punc_level KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: Controls the level of punctuation spoken as the screen is displayed, not reviewed. Levels range from zero no punctuation, to four, all punctuation. One corresponds to punc_some, two corresponds to punc_most, and three as well as four both correspond to punc_all. Some hardware synthesizers may have different levels each corresponding to three and four for punc_level. Also note that if punc_level is set to zero, and key_echo is set to
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
On Mon, Sep 16, 2019 at 03:47:28PM +0200, Samuel Thibault wrote: > Okash Khawaja, le dim. 15 sept. 2019 19:41:30 +0100, a ecrit: > > I have attached the descriptions. > > Attachment is missing :) > > Samuel Samuel, check the message that came to you directly, and it should be there. The speakup list rejects attachments. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
On Sun, Sep 08, 2019 at 10:43:02AM +0100, Okash Khawaja wrote: > Sorry, I have only now got round to working on this. It's not complete > yet but I have assimilated the feedback and converted subjective > phrases, like "I think..." into objective statements or put them in > TODO: so that someone else may verify. I have attached it to this > email. I think bleeps needs a TODO, since we don't know what values it accepts, or what difference those values make. Also, to keep things uniform, we should replace my "don't know" for trigger_time with a TODO. Looks good to me otherwise. Thanks. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
On Wed, Aug 21, 2019 at 09:39:25AM -0700, Okash Khawaja wrote: > Hi Greg N, > > Would like to send this as a patch as Greg K-H suggested? If not, I > can do that with your email in Authored-by: tag? > > Thanks, > Okash Hi Okash and all, feel free to submit the patch with my email in the Authored-by: tag if that's OK. Thanks, and good luck on your presentation. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
On Fri, Jul 12, 2019 at 05:46:23PM -0700, Gregory Nowak wrote: > On Fri, Jul 12, 2019 at 11:23:19AM +0200, Samuel Thibault wrote: > > Hello, > > > > To readers of the linux-speakup: could you help on this so we can get > > Speakup in mainline? Neither Okash or I completely know what user > > consequences the files in /sys/accessibility/speakup/ have, so could > > people give brief explanations for each file (something like 3-6 lines > > of explanation)? > > I have a recollection of documenting most of this on the speakup list > in response to a similar query a number of years ago. Unfortunately, > the speakup mailing list archives aren't easily searchable, and I > don't have a local copy of that mail. > > Kirk, doing grep with a few of the file names in > /sys/accessibility/speakup against the list's mbox file archive should > find that message if it's in fact there. If you can please find it, > and post the date when it was sent, we can provide a URL to that > thread as a starting point. If my recollection is wrong, and such a > message isn't in the archives, I'll write up what I know about. I've located the message I was thinking of in the archives, but that describes some speakup key commands, not /sys/accessibility/speakup. So, here's what I know, and hopefully someone else can fill in the rest. attrib_bleep Beeps the PC speaker when there is an attribute change such as foreground or background color when using speakup review commands. One = on, zero = off. I'm not currently at a machine with a working PC speaker, so can't test this right now. bell_pos As far as I know, this works much like a typewriter bell. If for example 72 is echoed to bell_pos, it will beep the PC speaker when typing on a line past character 72. Again, no PC speaker at the moment here, so can't actually test this. bleeps Not 100% sure, but I believe this controls whether one hears beeps through the PC speaker when using speakup's review commands. If no one jumps in on this, I'll experiment when at a machine with a working PC speaker, and will reply back with details. bleep_time Again, not 100% sure, but I believe this controls the duration of the PC speaker beeps speakup produces. I'm not sure of the units this is in either, possibly jiffys. I'll come back with more details on this one if no one else does. cursor_time Don't know. delimiters Don't know. I've tried echoing various characters to this and looking for differences when reviewing the screen, but no luck. ex_num Don't know. key_echo Controls if speakup speaks keys when they are typed. One = on, zero = off or don't echo keys. keymap I believe this is the currently active kernel keymap. I'm not sure of the format, probably what dumpkeys(1) and showkey(1) use. Echoing different values here should allow for remapping speakup's review commands besides remapping the keyboard as a whole. no_interrupt Controls if typing interrupts output from speakup. With no_interrupt set to zero, typing on the keyboard will interrupt speakup if for example the say screen command is used before the entire screen is read. With no_interrupt set to one, if the say screen command is used, and one then types on the keyboard, speakup will continue to say the whole screen regardless until it finishes. punc_all This is a list of all the punctuation speakup should speak when punc_level is set to four. punc_level Controls the level of punctuation spoken as the screen is displayed, not reviewed. Levels range from zero no punctuation, to four, all punctuation. As far as I can tell, one corresponds to punc_some, two corresponds to punc_most, and three as well as four seem to both correspond to punc_all, though I do stand to be corrected. I am using the soft synthesizer driver, so it is possible that some hardware synthesizers have different levels each corresponding to three and four for punc_level. Also note that if punc_level is set to zero, and key_echo is set to one, typed punctuation is still spoken as it is typed. punc_most This is a list of all the punctuation speakup should speak when punc_level is set to two. punc_some This is a list of all the punctuation speakup should speak when punc_level is set to one. reading_punc Almost the same as punc_level, the differences being that reading_punc controls the level of punctuation when reviewing the screen with speakup's screen review commands. The other difference is that reading_punc set to three speaks punc_all, and reading_punc set to four speaks all punctuation, including spaces. repeats a list of characters speakup repeats. Normally, when there are more than three characters in a row, speakup just reads three of those characters. For example, ".." would be read as dot, dot, dot. If a . is added to the list of characters in repeats, ".." would be read as dot, dot, dot, times six. say_control If set to one, speakup spe
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
On Fri, Jul 12, 2019 at 11:23:19AM +0200, Samuel Thibault wrote: > Hello, > > To readers of the linux-speakup: could you help on this so we can get > Speakup in mainline? Neither Okash or I completely know what user > consequences the files in /sys/accessibility/speakup/ have, so could > people give brief explanations for each file (something like 3-6 lines > of explanation)? I have a recollection of documenting most of this on the speakup list in response to a similar query a number of years ago. Unfortunately, the speakup mailing list archives aren't easily searchable, and I don't have a local copy of that mail. Kirk, doing grep with a few of the file names in /sys/accessibility/speakup against the list's mbox file archive should find that message if it's in fact there. If you can please find it, and post the date when it was sent, we can provide a URL to that thread as a starting point. If my recollection is wrong, and such a message isn't in the archives, I'll write up what I know about. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: [PATCH] staging: speakup: refactor synths array to use a list
On Tue, Jun 12, 2018 at 08:31:06AM +0200, Samuel Thibault wrote: > The load/unload is about the module itself, i.e. modprobe speakup_bns ; > modprobe speakup_soft, switch between them, then rmmod speakup_bns ; > speakup_soft or the converse (to exercise both orders). # uname -a Linux p41box 4.17.1 #1 SMP Sat Jun 16 11:19:57 MST 2018 i686 GNU/Linux # lsmod |grep "speakup" speakup_bns16384 0 speakup_soft 16384 1 speakup94208 3 speakup_bns,speakup_soft With /sys/accessibility/speakup/synth set to bns, I am getting output alternately from the bns and from soft. It's as if speakup can't make up its mind which synthesizer is being used. When I echo soft >/sys/accessibility/speakup/synth, I get no speech at all from either synthesizer. Doing rmmod of all three speakup modules comes back with no errors. There is also no unusual output in dmesg, I can see both synthesizers being registered and unregistered as I switch between them. I can also reproduce this behavior with speakup_soft, and speakup_dummy specifically: 1. modprobe speakup_soft and modprobe speakup_dummy 2. The synthesizer should now be set to dummy in /sys/accessibility/speakup/synth. 3. Use the speakup review keys, press enter a number of times. You should observe output from both the software speech, and from the serial port alternating between each other. 4. echo soft >/sys/accessibility/speakup/synth 5. You should observe no output from either software speech or the serial port as you use speakup review keys, or press enter repeatedly. 6. echo dummy >/sys/accessibility/speakup/synth 7. You should alternately get speech from the software synthesizer and from the serial port. I built my kernel from the 4.17.1 kernel.org sources, and the patch that Samuel reposted applied cleanly with no errors. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: [PATCH] staging: speakup: refactor synths array to use a list
On Tue, Jun 12, 2018 at 12:57:03AM +0200, Samuel Thibault wrote: > Anybody up for testing please? > > If people want to see speakup get mainlined instead of staging, please > help. If I understand right, this patch changes how synthesizers are loaded and unloaded through /sys/accessibility/speakup/synth, correct? If yes, then would for example verifying that echo bns >/sys/accessibility/speakup/synth echo soft >/sys/accessibility/speakup/synth does what it should be good enough of a test? If this would not be good enough, please describe exactly what needs testing. I likely won't be able to do a kernel build until this weekend, but should be able to report back next Monday on the 18th. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
