From: Greg KH <gregkh@linuxfoundation.org>
To: Dmitriy Fitisov <dmitriy@radier.ca>
Cc: linux-serial@vger.kernel.org
Subject: Re: Making our own device work under Linux
Date: Fri, 28 Nov 2014 10:48:45 -0800 [thread overview]
Message-ID: <20141128184845.GA30162@kroah.com> (raw)
In-Reply-To: <37235F81-C73A-4CBB-A4ED-C1B9B8D8182D@radier.ca>
On Fri, Nov 28, 2014 at 01:39:36PM -0500, Dmitriy Fitisov wrote:
> Hello everyone,
> we have made our own device using STM32 chip and it works well under Windows using serial communication
> through USB.
> We used ST Micro supplied driver and firmware example.
>
> Now we have a task to make it work under Linux.
> USB configuration is declared it as CDC modem, therefore Linux pickups cdc-acm driver and attach it to the device.
> I tested it under Ununtu and it seems that once device is attached some program
> tests it using AT commands. I would guess it is ModemManager which is started in /etc/init/modemmanager.conf
> I updated firmware on our device to process those commands, now I think I may simply remove ModemManager from startup and it would be fine.
>
> But our final platform should be Raspberry.
> It seems init here a little bit different, I do not see initctl program, man init differs and I'm getting different data on my device.
> It sounds like terminal sequence, with lot of "0x20 0x08" bytes after start sequence.
>
> So, I need to find out what program/daemon/service trying to communicate with cdc-acm.
> Is there a simple easy way without recompiling kernel with debug info?
There are lots of different distros for the Raspberry Pi, I would
suggest asking on the mailing list of the distro you are using to try to
determine this, as the people there will be able to help you out the
best.
Good luck,
greg k-h
next prev parent reply other threads:[~2014-11-28 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 18:39 Making our own device work under Linux Dmitriy Fitisov
2014-11-28 18:48 ` Greg KH [this message]
2014-11-28 19:05 ` Dmitriy Fitisov
2014-11-28 19:08 ` 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=20141128184845.GA30162@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dmitriy@radier.ca \
--cc=linux-serial@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).