[9fans] FW: FW: FW: bootsetup failure on 9legacy

2014-04-21 Thread Jan
I've had problems with 9atom when setting any resolution above the default, 1024x768x16 for example renders a black screen with several glitched colours. All the Plan 9 based software just seems to dislike my Thinkpad. From: 9fans-boun...@9fans.net [9fans-

Re: [9fans] What happened on lib9p?

2014-04-21 Thread kokamoto
Thanks cinap > i used this to make usb drivers multithreaded. Wow! I found also many eqlock() call instead of qlock(). Is this also related to usb slowness? Kenji

Re: [9fans] What happened on lib9p?

2014-04-21 Thread cinap_lenrek
no, it is not. in the kernel, you can only have one process doing a sleep on a rendezvous point at a time. so when you have multiple waiter processes, you put a qlock arround the sleep so the first process goes into the sleep and follow up processes will get queued on the qlock. the problem with

Re: [9fans] FW: FW: FW: bootsetup failure on 9legacy

2014-04-21 Thread erik quanstrom
On Mon Apr 21 03:18:44 EDT 2014, j...@margolius.co.uk wrote: > I've had problems with 9atom when setting any resolution above the > default, 1024x768x16 for example renders a black screen with several > glitched colours. odd. it would be interesting to see the output of aux/realemu

Re: [9fans] What happened on lib9p?

2014-04-21 Thread kokamoto
> the eqlock() is a interruptable version of > the qlock() call. that is, it can error out > when the process receives a note. Thans cinap! I'm checking how I can incorporate your nusb codes into my 'sources' conservative version usb codes. Of course, it's should be my personal hiden version.☺ B