mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "John G. Heim" <jheim@math.wisc.edu>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: speakup bug
Date: Sat, 3 Mar 2012 20:03:48 -0600	[thread overview]
Message-ID: <D9E4F6D133A2410EA4A56217E18CBAD7@hinkle> (raw)
In-Reply-To: <20120303173916.7eca9391@pyramind.ukuu.org.uk>

From: Alan Cox
Sent: Saturday, March 03, 2012 11:39 AM
Subject: Re: speakup bug

>> returns an error code. But it looks as if the region for a serial port,
>> 0x3f8 - 0x3ff,  in ioport_resource cannot be reserved because the entire
>> range from 0x000 through 0xcf7 is already taken by something named "PCI 
>> Bus
>> 0000:00".  Therefore calling request_resource always fails and the driver
> f>or the speech synth errors out.
>
>It's a heirarchical space, so you can allocate things within it. Look
>at /proc/ioports.

# file /proc/ioports
/proc/ioports: empty

>From looking at the code in resource.c, I don't know how you'd get a piece 
of an already allocated range.

It looks like fixing the speakup code to do serial ports right is a lot of 
work. Maybe we can just fix this problem in the mean time.


  parent reply	other threads:[~2012-03-04  2:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-03 17:18 John G. Heim
2012-03-03 17:39 ` Alan Cox
2012-03-03 22:01   ` Ted Ts'o
2012-03-04  0:01   ` John G. Heim
2012-03-04  0:18     ` Samuel Thibault
2012-03-04  0:21       ` Samuel Thibault
2012-03-04  0:41         ` Ted Ts'o
2012-03-04  0:43           ` Samuel Thibault
2012-03-04  0:44             ` Samuel Thibault
2012-03-04  1:41             ` Ted Ts'o
2012-03-04  0:26     ` Ted Ts'o
2012-03-04  2:03   ` John G. Heim [this message]
2012-03-04 21:06     ` Alan Cox

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=D9E4F6D133A2410EA4A56217E18CBAD7@hinkle \
    --to=jheim@math.wisc.edu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®