Re: [9front] recent kernel changes break built-in wacom serial tablet on

[cinap_lenrek@felloff.net]

interesting.

there was some changes in how the console uarts get initialized,
however, given that you can still change the cursor horizontally
means we'r receiving bytes from the tablet fine. maybe it
was caused by scheduler changes...

it seems that the code that tries to re-synchronize with the
packet stream is somehow desynchronized.

the code basically looks for a start byte "head" that has bit 7 (0x80)
set and then assume 9 more bytes for the full packet afterwards:

int
findheader(Tablet* t)
{
	uchar c;
	
	do {
		if(read(t->ser, &c, 1) < 1) return -1;
	} while((c & 0x80) == 0);
	return c;
}

Message*
readpacket(Tablet* t)
{
	uchar buf[9];
	int head;
	Message *m;

	head = findheader(t);
	if(head < 0) return 0;
	if(readn(t->ser, buf, 9) < 9) return 0;
	
	m = calloc(sizeof(Message), 1);
	incref(m);
	
	m->b = head & 7;
	m->x = (buf[0] << 9) | (buf[1] << 2) | ((buf[5] >> 5) & 3);
	m->y = (buf[2] << 9) | (buf[3] << 2) | ((buf[5] >> 3) & 3);
	m->p = ((buf[5] & 7) << 7) | buf[4];
	
	m->p *= MAX;
	m->p /= t->pmax;
	m->x *= t->sx;
	m->x /= t->xmax;
	m->y *= t->sy;
	m->y /= t->ymax;
	
	m->msg = smprint("m %d %d %d %d\n", m->x, m->y, m->b, m->p);
	return m;
}

i'd start debugging here. it is possible there is some crap in
the uart fifo when we switch the baud-rate and the re-synchronizatoin
code fails to recover from that.

also the serial mode might be different? maybe it is trying todo
software flow-control or something? can you cat:

cat /dev/eia2status

maybe one test you could do is using dd with a block size of 10 bytes:

</dev/eia2data {while(){dd -bs 10 -count 1 | xd -x1}}

--
cinap