linux-kernel - Re: r6080 driver not working.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 17 Oct 2008 20:46:46 +0200
From:	"Pieter Steyn" <pieterste@...il.com>
To:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Cc:	tech@....com.tw
Subject: Re: r6080 driver not working.

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

Cheers,
Pieter Steyn

On Fri, Oct 17, 2008 at 4:50 PM, Pieter Steyn <pieterste@...il.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.
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/