When moving the most usb driver out of staging, we forgot to remove the
subdirectory out of the staging Makefile as well.
Fixes: 97a6f772f36b ("drivers: most: add USB adapter driver")
Cc: Christian Gromm
Reported-by: Michael Straube
Signed-off-by: Greg Kroah-Hartman
---
drivers/st
Hey all,
I am a newbie Linux programmer, with nothing to credit myself with,
other than some boiling passion to develop a driver for a USB data card.
Heck, I couldn't write one for a mass storage device even, as I am
totally lost in how SCSI commands are formatted. Would like to join in
somet
On Mon, Jun 09, 2014 at 02:14:38PM +0900, Magnus Damm wrote:
> On Sat, Jun 7, 2014 at 12:39 AM, Greg KH wrote:
> > On Fri, Jun 06, 2014 at 07:44:08PM +0900, Magnus Damm wrote:
> >> staging: Emma Mobile USB driver and KZM9D board code V3
> >>
> >> [PATCH v
On Sat, Jun 7, 2014 at 12:39 AM, Greg KH wrote:
> On Fri, Jun 06, 2014 at 07:44:08PM +0900, Magnus Damm wrote:
>> staging: Emma Mobile USB driver and KZM9D board code V3
>>
>> [PATCH v3 01/05] staging: emxx_udc: Add Emma Mobile USB Gadget driver
>> [PATCH v3 02/05] st
On Fri, Jun 06, 2014 at 07:44:08PM +0900, Magnus Damm wrote:
> staging: Emma Mobile USB driver and KZM9D board code V3
>
> [PATCH v3 01/05] staging: emxx_udc: Add Emma Mobile USB Gadget driver
> [PATCH v3 02/05] staging: emxx_udc: I/O memory and IRQ resource support
> [PATCH v3
staging: Emma Mobile USB driver and KZM9D board code V3
[PATCH v3 01/05] staging: emxx_udc: Add Emma Mobile USB Gadget driver
[PATCH v3 02/05] staging: emxx_udc: I/O memory and IRQ resource support
[PATCH v3 03/05] staging: emxx_udc: Add TODO file
[PATCH v3 04/05] staging: board: Initial board
staging: Emma Mobile USB driver and KZM9D board code V2
[PATCH v2 01/05] staging: emxx_udc: Add Emma Mobile USB Gadget driver
[PATCH v2 02/05] staging: emxx_udc: I/O memory and IRQ resource support
[PATCH v2 03/05] staging: emxx_udc: Add TODO file
[PATCH v2 04/05] staging: board: Initial board
On Thu, May 22, 2014 at 06:32:03PM +0900, Magnus Damm wrote:
> Hi Dan,
>
> On Thu, May 22, 2014 at 6:17 PM, Dan Carpenter
> wrote:
> > Generally we take things as is into staging so there is no need for a
> > re-work if you don't want to. But we do need a TODO file. Read the
> > TODO files for
Hi Geert,
On Thu, May 22, 2014 at 6:21 PM, Geert Uytterhoeven
wrote:
> Hi Magnus,
>
> Thanks for your series! This looks like a good solution for interim board
> support.
Thanks!
> On Thu, May 22, 2014 at 10:53 AM, Magnus Damm wrote:
>> Olof, patch 3/3 contains some board staging code for KZM9
Hi Dan,
On Thu, May 22, 2014 at 6:17 PM, Dan Carpenter wrote:
> Generally we take things as is into staging so there is no need for a
> re-work if you don't want to. But we do need a TODO file. Read the
> TODO files for other staging drivers.
Thanks for pointing that out, my apologies for bein
Hi Magnus,
Thanks for your series! This looks like a good solution for interim board
support.
On Thu, May 22, 2014 at 10:53 AM, Magnus Damm wrote:
> Olof, patch 3/3 contains some board staging code for KZM9D. As it is
> today the EMEV2 SoC is DT-only and we neither have defconfig nor Kconfig
> d
Generally we take things as is into staging so there is no need for a
re-work if you don't want to. But we do need a TODO file. Read the
TODO files for other staging drivers.
regards,
dan carpenter
___
devel mailing list
de...@linuxdriverproject.org
h
Emma Mobile USB driver and KZM9D board code
[PATCH 01/03] staging: emxx_udc: Add Emma Mobile USB Gadget driver
[PATCH 02/03] staging: emxx_udc: I/O memory and IRQ resource support
[PATCH 03/03] staging: board: kzm9d: Board staging support for emxx_udc
This patch series contains an old USB Gadget
On Wed, Mar 05, 2014 at 10:36:53PM -0800, Kalyan Kodamagula wrote:
> Hi,
>
> Iam new to this ML,I need info regarding Usb device drivers.I had learned
> Lnx device drivers and having
> knowledge on USB Host driver(highlevel).
>
> I had seen probe/read/write functions of a driver.As there is
Hi,
Iam new to this ML,I need info regarding Usb device drivers.I had learned Lnx
device drivers and having
knowledge on USB Host driver(highlevel).
I had seen probe/read/write functions of a driver.As there is no need to
write drivers from scratch,we can gain knowledge by fixing some bugs
On Mon, Feb 03, 2014 at 08:35:06PM +0200, Aaro Koskinen wrote:
> Hi,
>
> On Wed, Dec 04, 2013 at 03:29:53PM -0800, Greg Kroah-Hartman wrote:
> > On Tue, Dec 03, 2013 at 11:46:50AM -0800, David Daney wrote:
> > > From: David Daney
> > >
> > > Tested against both EdgeRouter LITE (no bootloader sup
Hi,
On Wed, Dec 04, 2013 at 03:29:53PM -0800, Greg Kroah-Hartman wrote:
> On Tue, Dec 03, 2013 at 11:46:50AM -0800, David Daney wrote:
> > From: David Daney
> >
> > Tested against both EdgeRouter LITE (no bootloader supplied device
> > tree), and ebb5610 (device tree supplied by bootloader).
> >
On Thu, Jul 25, 2013 at 02:56:51PM +0900, Won Kang wrote:
> Anyway, you are right that endianess matters only when using this SDK.
> If you suggest to remove the ioctl because SDK is optional, I will
> agree.
Thanks, I've now removed it from the driver.
greg k-h
__
>> GDM7240 is in LE where as GDM7243 (currently under development) is in BE.
>
> But why does this information need to be sent to userspace?
>
GDM724x chips have different endianess because of their internal
architecture.The device sends out and accepts LTE protocol information
in its own endianes
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Thu, Jul 25, 2013 at 01:15:07PM +0900, Won Kang wrote:
> GDM7240 is in LE where as GDM7243 (currently under development) is in BE.
But why does this information need to be sent to userspace?
> Use
GDM7240 is in LE where as GDM7243 (currently under development) is in BE.
User space applications needs to discover the endianess to properly
encode/decode LTE control protocols. We have existing customers
already deploying units in large volume, and want to avoid forcing
them to change SDK APIs a
On Thu, Jul 25, 2013 at 12:53:40AM +0300, Dan Carpenter wrote:
> > +static int gdm_lte_ioctl_get_data(struct wm_req_t *req, struct net_device
> > *dev)
> > +{
> > + u16 id = req->data_id;
> > +
> > + switch (id) {
> > + case GET_ENDIAN_INFO:
> > + /* required for the user space app
> +static int gdm_lte_ioctl_get_data(struct wm_req_t *req, struct net_device
> *dev)
> +{
> + u16 id = req->data_id;
> +
> + switch (id) {
> + case GET_ENDIAN_INFO:
> + /* required for the user space application to find out device
> endian */
> + get_dev_endian
On Thu, Jul 25, 2013 at 03:36:17AM +0900, Won Kang wrote:
> +- Explain reason for multiples of 512 bytes in alloc_tx_struct()
Actually I remembered that I had seen this before in gdm_usb_send()
from drivers/staging/gdm72xx/gdm_usb.c. Apparently there is a
firmware bug.
/*
* In s
On Thu, Jul 25, 2013 at 03:36:17AM +0900, Won Kang wrote:
> GCT Semiconductor GDM7240 is 4G LTE chip.
> This driver supports GCT reference platform as a USB device.
I've applied this now, and fixed up the tty build warnings (which you
should have also seen.) I'm not sure I got the tty fixes corre
Hi Joe,
Got it. Thanks
Regards,
Won
원본 메시지
발신: Joe Perches
날짜: 2013/07/25 오전 3:42 (GMT+09:00)
수신: Won Kang
참조:
linux-ker...@vger.kernel.org,de...@driverdev.osuosl.org,gre...@linuxfoundation.org,Won
Kang
제목: Re: [PATCH v2 1/2] staging: gdm7240: adding LTE USB driver
On
On Thu, 2013-07-25 at 03:36 +0900, Won Kang wrote:
> GCT Semiconductor GDM7240 is 4G LTE chip.
> This driver supports GCT reference platform as a USB device.
>
> Signed-off-by: Won Kang
>
> staging: gdm7240: added contacts for code maintanance
>
> Signed-off-by: Won Kang
>
> staging: gdm7240:
On Wed, Jul 24, 2013 at 05:45:34PM +0900, Won Kang wrote:
> Hi Dan,
>
> Thanks, I am fixing the codes now. I plan to send v2 soon. However,
> most of them are syntactic and style issues, not logical ones.
> Probably they are due to the proprietary protocols being used between
> the device and the
Hi Dan,
Thanks, I am fixing the codes now. I plan to send v2 soon. However,
most of them are syntactic and style issues, not logical ones.
Probably they are due to the proprietary protocols being used between
the device and the host, and I do not have enough information to fix
those. I will have t
On Tue, Jul 23, 2013 at 11:43:52AM +0300, Dan Carpenter wrote:
> On Tue, Jul 23, 2013 at 04:40:29PM +0900, Won Kang wrote:
> > Thank you so much for the review. I will try to fix them soon.
> > Should I continue to send patches until reviewers agrees to accept
> > them? I have no experience with su
why the complaint is wrong. Resend the patch with a
[patch 1/2 v2] staging: gdm7240: adding LTE USB driver
After the signed off by line put:
Signed-off-by: You
---
v2: cleanup and minor fixes
The same for version 3 and so on.
This is a network driver so you really need to CC netdev and
lin
31 matches
Mail list logo
