Re: [PATCH v2 1/2] staging: gdm7240: adding LTE USB driver
From: Greg KH
Date: Thu Jul 25 2013 - 00:36:51 EST
Q: Should I include quotations after my reply?
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?
> 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 along with kernel updates.
> At some point, It will have to be fixed with SDK API can interoperate properly.
Ugh, really? What special tools does userspace need to talk to this
device? It "should" just be a network device, and a serial port, why
does the endianness of the device mean anything?
Custom ioctls aren't ok for new drivers, if at all possible. Can't
userspace just trigger this based on the device id instead?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/