From: Christian Gagneraud <cgagneraud@techworks.ie>
To: Wolfgang Rosner <wrosner@tirnet.de>
Cc: linux-serial@vger.kernel.org
Subject: Re: CMUX / ts710 serial multiplex driver for x86_64 architecture
Date: Sun, 04 Jan 2009 23:22:18 +0000 [thread overview]
Message-ID: <496144AA.8000506@techworks.ie> (raw)
In-Reply-To: <200901042310.22171.wrosner@tirnet.de>
Wolfgang Rosner wrote:
> Dear kernel professionals,
>
> I'm dealing with a mobile unit development kit that requires multiplexing of
> several virtual serial lines over one single physical serial.
> The protocol is supposed to follow GSM 07.10 standard and outlined in detail
> here:
> http://www.roundsolutions.com/techdocs/docs/30268st10299a_CMUX_User_Guide_r2.pdf
>
> The supplier only supports WIN :-( drivers.
> There appear to be kernel modules around for embedded linux.
> I tried to download one
> http://svn.openezx.org/trunk/src/kernel-2.6/mux/
> but could not manage to build it in my x86_64 environment.
>
> At the moment, I have no idea whether this module might fulfil my purpose at
> all.
> Maybe it only implements the module side (i.e. pretending a mobile device),
> not the application side (the controlling PC).
> What I expect is to load this (presumably with some userspace action and
> synchronisation commands to the controlled device) ontop of an existing
> serial connection. As a result, there should be some additional serial
> devices, where the demux'ed traffic can be piped in and out.
>
> I find clues that this type of multiplexing is done e.g in some mobile connect
> utilities, but nowhere (apart from the link given above) I find a dedicated
> kernel module for right that purpose.
>
>
> So here my questions:
> - Is there a version of the above mentioned mux / mux_river / ts0710 / mux_cli
> for x86_64 available?
> - or could this one from be adapted?
> - is there another implementation of GSM 07.10 MUXing?
> - is there any documentation around?
Hi Wolfgang,
These links might help you:
http://wiki.openmoko.org/wiki/Roadmap/Telephony
http://developer.berlios.de/projects/gsmmux/
Chris
>
> Although the issue is not core critical for my project, I'd like to contribute
> if I can. No problem with testing and supplying docs, I think.
> Simple userspace config tool (e.g. some perl script writing/reading some bits
> to /proc/whats/o/ever) should still be within my capabilities.
>
> In some ancient time (2.0 or 2.2 kernel as far as I can remember) I have even
> managed to adopt and build a kernel module for some LC display from a book
> template, but that's years ago. But I'm not really firm in C, and things
> might not have become less complex since that days...
> But if I get help (some pointers where to start, caveats to look for) I might
> try it, provided there is a chance of success.
>
> Any help appreciated.
>
> Yours
> Wolfgang Rosner
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-serial" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-01-04 23:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-04 22:10 CMUX / ts710 serial multiplex driver for x86_64 architecture Wolfgang Rosner
2009-01-04 23:22 ` Christian Gagneraud [this message]
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=496144AA.8000506@techworks.ie \
--to=cgagneraud@techworks.ie \
--cc=linux-serial@vger.kernel.org \
--cc=wrosner@tirnet.de \
/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.