From: "John W. Linville" <linville@tuxdriver.com>
To: Jason Andryuk <jandryuk@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
gregkh@suse.de, kalle.valo@iki.fi
Subject: Re: [PATCH] at76_usb: fix bugs introduced by "Staging: at76_usb: cleanup dma on stack issues"
Date: Fri, 30 Jan 2009 09:05:03 -0500 [thread overview]
Message-ID: <20090130140503.GC3485@tuxdriver.com> (raw)
In-Reply-To: <c4d76b3b0901292059w20fccf62gdae10eee02ac4791@mail.gmail.com>
FWIW, that driver is in the staging tree. I'm not sure if there is
a mailing list for that or not, but you should at least copy Greg on
any patches. Kalle might be interested in seeing them too.
Hth!
John
On Thu, Jan 29, 2009 at 11:59:48PM -0500, Jason Andryuk wrote:
> Tracking down the firmware loading problem led to this commit.
>
> $ git bisect bad
> 0d1d1424330cc1934f2b2742f0cfa2c31e6a250b is first bad commit
> commit 0d1d1424330cc1934f2b2742f0cfa2c31e6a250b
> Author: Oliver Neukum <oliver@neukum.org>
> Date: Thu Dec 18 13:16:40 2008 +0100
>
> Staging: at76_usb: cleanup dma on stack issues
>
> - no DMA on stack
> - cleanup unclear endianness issue
>
> Signed-off-by: Oliver Neukum <oneukum@suse.de>
> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
>
> :040000 040000 c4fee9ea0fef25926229d810d19dc2f89cca9401
> 8b165a35d16280d2413b2700a6080ef290ca1009 M drivers
>
> The "no DMA on stack" conversion was incomplete with respect to
> updating the arguments passed to usb_control_msg. The value 40 is
> hardcoded as it was prior to conversion.
>
> The driver can now load firmware, but is not fully functional.
>
> Signed-off-by: Jason Andryuk <jandryuk@gmail.com>
> --
>
> diff --git a/drivers/staging/at76_usb/at76_usb.c b/drivers/staging/at76_usb/at76
> index 185533e..befde9b 100644
> --- a/drivers/staging/at76_usb/at76_usb.c
> +++ b/drivers/staging/at76_usb/at76_usb.c
> @@ -598,7 +598,7 @@ static int at76_get_op_mode(struct usb_device *udev)
> return -ENOMEM;
> ret = usb_control_msg(udev, usb_rcvctrlpipe(udev, 0), 0x33,
> USB_TYPE_VENDOR | USB_DIR_IN |
> - USB_RECIP_INTERFACE, 0x01, 0, &op_mode, 1,
> + USB_RECIP_INTERFACE, 0x01, 0, op_mode, 1,
> USB_CTRL_GET_TIMEOUT);
> saved = *op_mode;
> kfree(op_mode);
> @@ -731,7 +731,7 @@ static inline int at76_get_cmd_status(struct usb_device *ude
> ret = usb_control_msg(udev, usb_rcvctrlpipe(udev, 0), 0x22,
> USB_TYPE_VENDOR | USB_DIR_IN |
> USB_RECIP_INTERFACE, cmd, 0, stat_buf,
> - sizeof(stat_buf), USB_CTRL_GET_TIMEOUT);
> + 40, USB_CTRL_GET_TIMEOUT);
> if (ret >= 0)
> ret = stat_buf[5];
> kfree(stat_buf);
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2009-01-30 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 4:59 [PATCH] at76_usb: fix bugs introduced by "Staging: at76_usb: cleanup dma on stack issues" Jason Andryuk
2009-01-30 14:05 ` John W. Linville [this message]
2009-02-04 1:26 ` patch staging-at76_usb-fix-bugs-introduced-by-staging-at76_usb-cleanup-dma-on-stack-issues.patch added to gregkh-2.6 tree gregkh
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=20090130140503.GC3485@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=gregkh@suse.de \
--cc=jandryuk@gmail.com \
--cc=kalle.valo@iki.fi \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).