mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Pieter Steyn" <pieterste@gmail.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: tech@dmp.com.tw
Subject: Re: r6080 driver not working.
Date: Fri, 17 Oct 2008 20:46:46 +0200	[thread overview]
Message-ID: <c49e66200810171146u5915c6b8w95174f97cdc92c89@mail.gmail.com> (raw)
In-Reply-To: <c49e66200810170750s2d06d035m28ce5da3e6ca9c38@mail.gmail.com>

Ugh, sorry.  I obviously meant the r6040 driver. :)

Cheers,
Pieter Steyn

On Fri, Oct 17, 2008 at 4:50 PM, Pieter Steyn <pieterste@gmail.com> wrote:
> Hi,
>
> I cannot get the r6080 driver working properly in either 2.6.26 or
> 2.6.27.  It compiles, and loads fine enough, but as soon as I try and
> bring up the device I get a 'resource is in use and busy' message.
>
> I've tried using both the driver supplied by the kernel and the one
> linked on their website (with some modifications to make it compile :
>
> r6040# diff r6040.c r6040.orig
> 277a278
>>       SET_MODULE_OWNER(dev);
> 380c381
> <       i = request_irq(dev->irq, &r6040_interrupt, IRQF_SHARED,
> dev->name, dev);
> ---
>>       i = request_irq(dev->irq, &r6040_interrupt, SA_SHIRQ, dev->name, dev);
> 1079c1080
> <       return pci_register_driver (&r6040_driver);
> ---
>>       return pci_module_init (&r6040_driver);
>
> Networking works with 2.6.21 using the driver from their website and
> the above patch.
>
> I've cc'ed in tech support to the manufacturer.
>
> Thanks, and sorry if the information isn't much to work with...but
> since I don't get any errors other than device being busy I'm not sure
> what to do from here.
>

  reply	other threads:[~2008-10-17 18:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-17 14:50 Pieter Steyn
2008-10-17 18:46 ` Pieter Steyn [this message]
2008-10-17 23:32   ` Florian Fainelli

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=c49e66200810171146u5915c6b8w95174f97cdc92c89@mail.gmail.com \
    --to=pieterste@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tech@dmp.com.tw \
    /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®