mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Roland Klabunde" <roland.klabunde@web.de>
To: <imesmits@xs4all.nl>, <linux-kernel@vger.kernel.org>
Cc: <r.klabunde@berkom.de>, <info@scitel.de>, <kkeil@suse.de>
Subject: Re: [PATCH] drivers/isdn/hisax/bkm_a8.c, kernel 2.4.2 (Scitel Quadro)
Date: Mon, 2 Apr 2001 19:58:00 +0200	[thread overview]
Message-ID: <003c01c0bb9e$851756a0$c70ca8c0@klabunde> (raw)
In-Reply-To: <3AC4A0A9.EA78984@xs4all.nl>

Hi all,

great to hear, that the fix solves the problem. Is there any information
about, whether and when the fix will migrate into the isdn4l source pool?

Roland



----- Original Message -----
From: <imesmits@xs4all.nl>
To: <linux-kernel@vger.kernel.org>
Cc: <r.klabunde@berkom.de>; <info@scitel.de>; <kkeil@suse.de>
Sent: Friday, March 30, 2001 5:05 PM
Subject: [PATCH] drivers/isdn/hisax/bkm_a8.c, kernel 2.4.2 (Scitel Quadro)


> Hi,
>
> Please find attached a patch to fix the following problems with the
> Scitel Quadro ISDN card in 2.4 kernels which suddenly arised when I
> bought
> a K7T Pro motherboard.
>
> kernel: HiSax: Scitel port 0xcc00-0xcd00 already in use
> kernel: HiSax: Card Scitel Quadro not installed !
>
> Credits go to Roland Klabunde who told me early december:
>
> <quote>
> The Scitel [...] resource requirements are as follows:
>
> - 1 shared interrupt for all controllers
> - 1 shared port address for all controllers with a range of 128 bytes
> - 1 port address for each controller with a range of 64 bytes
>
> [...]
>
> I've currently downloaded the ISDN stuff [...] As mentioned above, the
> span is *128* for pci_ioaddr1 and *64* for pci_ioaddr2 to pci_ioaddr5
> [...]. What I see from the source is, that one attempts to claim a
> range of 256 bytes for pci_ioaddr1 to _5. That may cause the problems
> if the range overlaps with other boards. You may try to change the
> following calls in bkm_a8.c:
>
> sct_alloc_io(pci_ioaddr1, 256) to sct_alloc_io(pci_ioaddr1, 128)
> sct_alloc_io(pci_ioaddr2, 256) to sct_alloc_io(pci_ioaddr1, 64)
> sct_alloc_io(pci_ioaddr3, 256) to sct_alloc_io(pci_ioaddr1, 64)
> sct_alloc_io(pci_ioaddr4, 256) to sct_alloc_io(pci_ioaddr1, 64)
> sct_alloc_io(pci_ioaddr5, 256) to sct_alloc_io(pci_ioaddr1, 64)
>
> Please note the necessary changes in release_io_sct_quadro.
> </quote>
>
> Too bad I went on a holiday that time and forgot all about it, untill
> today (shame shame shame). Anyway, this patch to 2.4.2
> drivers/isdn/hisax/bkm_a8.c fixes the problem and everything runs
> fine again.
>
> Ime Smits
>
>


      reply	other threads:[~2001-04-02 18:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-30 15:05 Ime Smits
2001-04-02 17:58 ` Roland Klabunde [this message]

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='003c01c0bb9e$851756a0$c70ca8c0@klabunde' \
    --to=roland.klabunde@web.de \
    --cc=imesmits@xs4all.nl \
    --cc=info@scitel.de \
    --cc=kkeil@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=r.klabunde@berkom.de \
    /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®