Send buglog mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.openmoko.org/mailman/listinfo/buglog
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of buglog digest..."
Today's Topics:
1. Re: Openmoko Bug #2180: stable-tracking: 'rxserr' UART
messages (Openmoko Public Trac)
2. Re: Openmoko Bug #2215: distros using fso-gsm0710muxd will
not register (Openmoko Public Trac)
3. Re: Openmoko Bug #2215: distros using fso-gsm0710muxd will
not register (Openmoko Public Trac)
--- Begin Message ---
#2180: stable-tracking: 'rxserr' UART messages
-----------------------------+----------------------------------------------
Reporter: laforge | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone: FSO
Component: System Software | Version:
Severity: major | Keywords: gps s3x24xx_serial rxerr
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by andy):
I looked at /dev/ttySAC0 with stty on GTA02 / FSO and the crtscts flag is
not set on it.
Quite aside from interrupt latencies, it should actually be impossible to
get RX FIFO overrun as seen by the RX UART anyway, when the UART is
dealing with the handshakes in hardware and the other side is honouring
them. It won't help with GPS case but that's of a different level of
symptom if we trash the occasional RX sentence compared to destroying the
GSM mux.
I confirmed that if we set it, with stty -F /dev/ttyUSB0 crtscts, then the
appropriate bit in the UART regs gets set to enable hardware management of
RTS.
What's the crtscts state on the glofiish ttySAC?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2180#comment:8>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2215: distros using fso-gsm0710muxd will not register
-----------------------------+----------------------------------------------
Reporter: BillK | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone: FSO
Component: System Software | Version:
Severity: normal | Keywords: gsm0710muxd GSM modem
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------------+----------------------------------------------
Comment(by BillK):
There should be a specific line discipline used for the ti-calypso in some
cases - and the ficgta01 multiplexor (in 2008.12 source) has it - the
gsm0710muxd does not set it that can I see:
in "ficgta01multiplexer.cpp":
bool Ficgta01MultiplexerPlugin::detect( QSerialIODevice *device )
{
// The FIC needs a special line discipline set on the device.
QSerialPort *port = qobject_cast<QSerialPort *>( device );
if (port) {
int discipline = N_TIHTC;
::ioctl(port->fd(), TIOCSETD, &discipline);
}
and:
http://www.handhelds.org/hypermail/htc-pxa/0/0089.html
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2215#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2215: distros using fso-gsm0710muxd will not register
-----------------------------+----------------------------------------------
Reporter: BillK | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone: FSO
Component: System Software | Version:
Severity: normal | Keywords: gsm0710muxd GSM modem
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------------+----------------------------------------------
Comment(by mickey):
The TIHTC line discipline has been developed for some HTC devices, it's
neither useful on our hardware nor present in our kernels. Qtopia's call
will just silently fail and I'm surprised to see it in there.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2215#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
