From: Greg KH <gregkh@linuxfoundation.org>
To: Won Kang <wkang77@gmail.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
devel@driverdev.osuosl.org, wonkang@gctsemi.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] staging: gdm7240: adding LTE USB driver
Date: Wed, 24 Jul 2013 21:37:41 -0700 [thread overview]
Message-ID: <20130725043741.GA11906@kroah.com> (raw)
In-Reply-To: <CABe_0=+bXAuXhG+XG4ObUO_2MYD_XWxF_wbTVrpKagmHi8_CDQ@mail.gmail.com>
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?
> 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?
thanks,
greg k-h
next prev parent reply other threads:[~2013-07-25 4:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 6:56 [PATCH 1/2] staging: gdm7240: adding LTE USB driver Won Kang
2013-07-22 6:56 ` [PATCH 2/2] staging: gdm7240: added contacts for code maintanance Won Kang
2013-07-22 7:29 ` Joe Perches
2013-07-22 15:13 ` Greg KH
2013-07-22 18:27 ` [PATCH 1/2] staging: gdm7240: adding LTE USB driver Dan Carpenter
2013-07-24 18:36 ` [PATCH v2 " Won Kang
2013-07-24 18:41 ` Joe Perches
2013-07-24 18:50 ` 회신: " Won Kang
2013-07-24 20:34 ` Greg KH
2013-07-24 21:08 ` Dan Carpenter
2013-07-24 21:53 ` Dan Carpenter
2013-07-24 22:06 ` Greg KH
2013-07-25 4:15 ` Won Kang
2013-07-25 4:37 ` Greg KH [this message]
2013-07-25 5:56 ` Won Kang
2013-07-25 17:01 ` Greg KH
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=20130725043741.GA11906@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wkang77@gmail.com \
--cc=wonkang@gctsemi.com \
/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