Josh Hansen | 1 Apr 2003 03:58
Picon

Siemens SX56 ipaq.o adaptation?

I just bought the Siemens SX56 PocketPC/Phone from AT&T wireless. I am 
looking into what it will take to sync this PDA with my Linux system, 
and I think the key thing preventing me from doing that is that the 
kernel, after recognizing that the SX56 is connected to the USB, doesn't 
have a driver that claims the device. The ipaq module I would think 
could recognize the device and facilitate serial communications with it, 
which is where userspace programs take over.

Anyway, my question is how big of a deal would it be to get driver 
support for this PDA?

- Josh Hansen

-
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Culos Alain | 4 Apr 2003 18:30
Picon

OT - seeking open source protocol analyser V24 & X21

Hi All,

I know this is somewhat Off Topic on this list, but you guys are all getting
your hands dirty with serial stuff so I thought some of you would know of :

- good Protocol Analyser Software (Linux or Windows) that is open source,
otherwise freely available or maybe even at moderate cost (Feline and family
are a little on the expensive side of things).

I'm looking for software that is able to tap into RS232/V24/DB25 as well as
X21/DB15 (provided I have the relevant hardware that is). Linux is good, but
windows would be great as I have many more of those available for use and
changing OS in those PCs is not an option).
I've seen some nifty package : Ethereal but it seems geared towards Ethernet
and related physical interfaces to the exclusion of serial interfaces.

If and you know anything of use for serial interface sniffing as above, I'd
love to hear from you (I'm not sure responses are of interest to the list,
you decide).

Many thanks in advance & regards,
Alain.

If you are in any doubt about the authenticity of this 
message please contact +353 1 6718655.

-
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
(Continue reading)

Mathur, Shobhit | 16 Apr 2003 02:40
Favicon

linux-source debugging with kgdb-patch

Hello,

BACKGROUND:

I was keen to see kgdb running  for  purely academic reasons. Thus,
I made a setup of 2 machines for source-level debugging of the
linux-kernel. The procedure mentioned on the web-site
[ kgdb.sourceforge.net] has  been adhered to.  I was able to
successfully configure the setup. Also, I decided to use "ddd" front-end
on gdb [local m/c]  for debugging  the kgdb-patched kernel on the remote
machine, which is the usual setup for such debugging-efforts.
    The m/c to be debugged stops with the message "Waiting for
connection from remote gdb..." until the "target remote" command is run
from the "gdb" prompt of "ddd", upon which the m/c to be debugged
continues it's bootup till it shows the command-prompt.

PROBLEM:

I was interested in setting a break-point in start_kernel thru' "ddd"
such that the boot-up  of the m/c to be debugged could be analysed
step-by-step remotely. Though, I am able to set the breakpoint in
start_kernel(),
the commands "run" or "continue" on the "gdb" prompt, only throw up the
following errors :

(gdb) info break
Num Type           Disp Enb Address    What
7   breakpoint      keep  y   0xc027e7f0 in start_kernel at
init/main.c:614
(gdb) run
(Continue reading)

Mathur, Shobhit | 17 Apr 2003 17:16
Favicon

linux-source debugging with kgdb-patch


Hello,

BACKGROUND:

I was keen to see kgdb running  for  purely academic reasons. Thus,
I made a setup of 2 machines for source-level debugging of the
linux-kernel. The procedure mentioned on the web-site
[ kgdb.sourceforge.net] has  been adhered to.  I was able to
successfully configure the setup. Also, I decided to use "ddd" front-end
on gdb [local m/c]  for debugging  the kgdb-patched kernel on the remote
machine, which is the usual setup for such debugging-efforts.
    The m/c to be debugged stops with the message "Waiting for
connection from remote gdb..." until the "target remote" command is run
from the "gdb" prompt of "ddd", upon which the m/c to be debugged
continues it's bootup till it shows the command-prompt.

PROBLEM:

I was interested in setting a break-point in start_kernel thru' "ddd"
such that the boot-up  of the m/c to be debugged could be analysed
step-by-step remotely. Though, I am able to set the breakpoint in
start_kernel(),
the commands "run" or "continue" on the "gdb" prompt, only throw up the
following errors :

(gdb) info break
Num Type           Disp Enb Address    What
7   breakpoint      keep  y   0xc027e7f0 in start_kernel at
init/main.c:614
(Continue reading)

Alex Moen | 17 Apr 2003 20:44
Favicon

Saving data from the serial port

Hey all,

I am willing to bet that:
  a) this is so simple that I am overlooking it, or
  b) it has been covered a MILLION times already.

If b, please let me know where to find the answer, because I can't find it.
If a, tell me how blockheaded I am, laugh a little, and then tell me the
solution....

I want to take the data from a serial port from our PBX and log it to a
file.  Sounds simple, right?  I can (Winblows) hyperterm to the port and
gather the data.  I can connect the port to a serial printer and get the
data.  But, when I connect my linux box to the serial port, I am only
getting PART of the data.  For instance, I am only getting the first 14-16
characters of each line, with really no line breaks.  I also notice with
statserial that I am getting an overrun (wth is that???).  I have the port
settings in the software set at what Windows and the printer are set at
(9600-8-N-1).

I have read through the serial howto, tried a few programs that are
suggested (two that look promising but are giving the above results are
linbar and logserial), and am stumped.

I'd hate to have to set up a Win98 box running hyperterm logging to a file,
and then manually rotate that each day....

Thanks, and don't laugh too hard...

Alex
(Continue reading)

Amit Kucheria | 17 Apr 2003 20:42

persistent SLIP connections

Hi,

I currently use 'slattach' (actually a modified version) to setup a SLIP
connection between two machines. But when I unplug the cable and replug
it back in, I have to reconfigure the connection at both end.

Could this be handled in the slattach program, so that it does not
'hangup' due to loss of DCD or DSR?

Regards,
Amit

--

-- 
----------------------------------------------------------------------
Amit Kucheria          akucheria <at> NOSPAMmetricsystems.com
Metric Systems Corp.   2320 Cousteau Court, Suite 201, Vista, CA 92083
----------------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Ed Vance | 17 Apr 2003 21:10

RE: Saving data from the serial port

On Thu, Apr 17, 2003 at 11:44 AM, Alex Moen wrote:
> 
> I want to take the data from a serial port from our PBX and 
> log it to a file.  Sounds simple, right?  I can (Winblows) 
> hyperterm to the port and gather the data.  I can connect 
> the port to a serial printer and get the data.  But, when I 
> connect my linux box to the serial port, I am only getting 
> PART of the data.  For instance, I am only getting the 
> first 14-16 characters of each line, with really no line 
> breaks.  I also notice with statserial that I am getting an 
> overrun (wth is that???).  I have the port settings in the 
> software set at what Windows and the printer are set at
> (9600-8-N-1).
> 
> I have read through the serial howto, tried a few programs 
> that are suggested (two that look promising but are giving 
> the above results are linbar and logserial), and am stumped.
> 
> I'd hate to have to set up a Win98 box running hyperterm 
> logging to a file, and then manually rotate that each day....
> 
Overruns happen when the UART receiver FIFO buffer is completely
full when the next date character is received. The byte that did
not fit is discarded and the overrun status is posted. 

the root cause is either that the data is not being read fast 
enough by the program, or system interrupt latency is too long
to let the driver service the UART before an overrun occurs. 

If the data source supports XON/XOFF or hardware flow control, 
(Continue reading)

Amit Kucheria | 17 Apr 2003 23:19

CONFIG_HARD_PPS ?

Hi,

I have been studying the serial driver code and found the following
chunk of code in serial.c (2.4.19):

---------------------------------------------------------------
#ifdef CONFIG_HARD_PPS
			if ((info->flags & ASYNC_HARDPPS_CD) &&
			    (status & UART_MSR_DCD))
				hardpps();
#endif
---------------------------------------------------------------

There seems to be no reference to it in the current 2.4 and 2.5 kernels.
There are some reference in the 2.2 kernels. Is this cruft left from
previous versions?

Regards,
Amit

--

-- 
----------------------------------------------------------------------
Amit Kucheria          akucheria <at> NOSPAMmetricsystems.com
Metric Systems Corp.   2320 Cousteau Court, Suite 201, Vista, CA 92083
----------------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
(Continue reading)

Matti Aarnio | 18 Apr 2003 00:15
Favicon

Re: CONFIG_HARD_PPS ?

On Thu, Apr 17, 2003 at 02:19:52PM -0700, Amit Kucheria wrote:
> Hi,
> 
> I have been studying the serial driver code and found the following
> chunk of code in serial.c (2.4.19):
> 
> ---------------------------------------------------------------
> #ifdef CONFIG_HARD_PPS
> 			if ((info->flags & ASYNC_HARDPPS_CD) &&
> 			    (status & UART_MSR_DCD))
> 				hardpps();
> #endif
> ---------------------------------------------------------------
> 
> There seems to be no reference to it in the current 2.4 and 2.5 kernels.
> There are some reference in the 2.2 kernels. Is this cruft left from
> previous versions?

Sort of.    That is used in externally synchronized time-master-keeper
code, where a "1 pulse per second" line from (these days) GPS receiver
is fed to serial port DCD input pin.

It is indeed pity that the full code-set isn't included in kernel
baseline.  More people could then use Linux as their NTP master.

> Regards,
> Amit
> Amit Kucheria          akucheria <at> NOSPAMmetricsystems.com
> Metric Systems Corp.   2320 Cousteau Court, Suite 201, Vista, CA 92083

(Continue reading)

george anzinger | 18 Apr 2003 02:26

Re: linux-source debugging with kgdb-patch

Mathur, Shobhit wrote:
> 
> 
> Hello,
> 
> BACKGROUND:
> 
> I was keen to see kgdb running  for  purely academic reasons. Thus,
> I made a setup of 2 machines for source-level debugging of the
> linux-kernel. The procedure mentioned on the web-site
> [ kgdb.sourceforge.net] has  been adhered to.  I was able to
> successfully configure the setup. Also, I decided to use "ddd" front-end
> on gdb [local m/c]  for debugging  the kgdb-patched kernel on the remote
> machine, which is the usual setup for such debugging-efforts.
>     The m/c to be debugged stops with the message "Waiting for
> connection from remote gdb..." until the "target remote" command is run
> from the "gdb" prompt of "ddd", upon which the m/c to be debugged
> continues it's bootup till it shows the command-prompt.
> 
> PROBLEM:
> 
> I was interested in setting a break-point in start_kernel thru' "ddd"
> such that the boot-up  of the m/c to be debugged could be analysed
> step-by-step remotely. Though, I am able to set the breakpoint in
> start_kernel(),
> the commands "run" or "continue" on the "gdb" prompt, only throw up the
> following errors :
> 
> (gdb) info break
> Num Type           Disp Enb Address    What
(Continue reading)


Gmane