From: Greg KH <greg@kroah.com>
To: Rodolfo Giometti <giometti@linux.it>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/1] Add c2 port support.
Date: Fri, 3 Oct 2008 14:59:23 -0700 [thread overview]
Message-ID: <20081003215923.GA14890@kroah.com> (raw)
In-Reply-To: <1223044589-31741-2-git-send-email-giometti@linux.it>
On Fri, Oct 03, 2008 at 04:36:29PM +0200, Rodolfo Giometti wrote:
> C2port implements a two wire serial communication protocol (bit
> banging) designed to enable in-system programming, debugging, and
> boundary-scan testing on low pin-count Silicon Labs devices.
>
> Currently this code supports only flash programming through sysfs
> interface but extensions shoud be easy to add.
>
> Signed-off-by: Rodolfo Giometti <giometti@linux.it>
> ---
> drivers/misc/Kconfig | 13 +
> drivers/misc/Makefile | 1 +
> drivers/misc/c2port_core.c | 996 ++++++++++++++++++++++++++++++++++++++++++++
> include/linux/c2port.h | 65 +++
Why does this file have to be in include/linux? I don't think this
exports any structures to userspace, and no other code calls this
driver, so it should all fit into the .c file just fine.
Also, please create the needed Documentation/ABI/ files for these new
sysfs entries, describing how they are used, and what the format of them
are.
Is there any way to detect automatically if this hardware is present in
the system or not?
Otherwise, how will it be loaded by a distro automatically?
thanks,
greg k-h
next prev parent reply other threads:[~2008-10-03 23:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 14:36 Support for Silicon C2 Interface Rodolfo Giometti
2008-10-03 14:36 ` [PATCH 1/1] Add c2 port support Rodolfo Giometti
2008-10-03 21:59 ` Greg KH [this message]
2008-10-07 9:38 ` Rodolfo Giometti
2008-10-07 17:30 ` Greg KH
2008-10-07 19:14 ` Rodolfo Giometti
2008-10-07 20:00 ` Greg KH
2008-10-07 20:27 ` Rodolfo Giometti
2008-10-03 14:49 ` Support for Silicon C2 Interface 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=20081003215923.GA14890@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=giometti@linux.it \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.