public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Wouter de Waal <wrm@ccii.co.za>
Cc: linux-kernel@vger.kernel.org
Subject: Re: FDDI on Linux kernel 2.6
Date: Tue, 24 Oct 2006 15:02:00 +0100	[thread overview]
Message-ID: <1161698520.22348.27.camel@localhost.localdomain> (raw)
In-Reply-To: <5.0.0.25.2.20061024131939.05e4de70@alpha.ccii.co.za>

Ar Maw, 2006-10-24 am 13:19 +0200, ysgrifennodd Wouter de Waal:
> We here at CCII Systems are probably the only company in the world still
> actively involved with FDDI. The Linux Syskonnect FDDI driver needs a
> patch. I have no idea who to speak to, but the g over at osdl said I
> must ask here.

This is the right starting point. There is a network development list
that might be better but I think essentially you might as well own the
driver if nobody else is laying any claim to it any more. 

> The second customer's problem could not be solved by the above. They
> eventually found that kernel 2.6 (specifically, 2.6.8) uses memory
> mapping, and that a check in the driver caused an exception because
> of the length of the PCI region being 2048 and not 16384 (0x4000).
> The customer reports that changing the compare to
> 
> >if (len < 2048) {
> 
> fixed the problem for them.
> 
> Can this patch be applied to the kernel please?

I suspect the correct check is (len < FP_IO_LEN)

Either you or your customer can send patches versus a current kernel to
update the driver.

Alan


  reply	other threads:[~2006-10-24 13:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-24 11:19 FDDI on Linux kernel 2.6 Wouter de Waal
2006-10-24 14:02 ` Alan Cox [this message]
2006-10-24 15:20 ` Lee Revell
2006-10-24 15:30   ` Maciej W. Rozycki

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=1161698520.22348.27.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wrm@ccii.co.za \
    /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