Minix 3 USB Stack (Unofficial) 0.01-alpha release
Althaf k Backer
Althaf k Backer
Niek Linnenbank
Screenshots
http://code.google.com/p/minix3-usbsubsystem/wiki/Screenshotsalpha17032010
--
You received this message because you are subscribed to the Google Groups "minix3" group.
To post to this group, send email to min...@googlegroups.com.
To unsubscribe from this group, send email to minix3+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/minix3?hl=en.
--
Niek Linnenbank
WWW: http://www.nieklinnenbank.nl/
BLOG: http://nieklinnenbank.wordpress.com/
FUN: http://www.FreeNOS.org/
Althaf k Backer
On Mar 18, 12:48 am, Niek Linnenbank <nieklinnenb...@gmail.com> wrote:
> Excellent work althaf. Congratulations!
Thank you Niek :-)
Al Pech
-
Evgeniy Ivanov
> --
> You received this message because you are subscribed to the Google Groups "minix3" group.
> To post to this group, send email to min...@googlegroups.com.
> To unsubscribe from this group, send email to minix3+un...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/minix3?hl=en.
>
>
--
Evgeniy Ivanov
Althaf
Have you tried yet ? just wanted to know if it worked
over there.
--
http://mykeystrokes.blogspot.com
“Unix is user-friendly. It's just very selective about who its friends are.”
"Study as if you were to live forever. Live as if you were to die tomorrow"
"The only thing that interferes with my learning is my education.
"-Albert Einstein
wufeng
Althaf
> Very good!
:-) , wufeng have you tired it , i haven't done much
testing to make sure it works fine on all.
Roman Ignatov
Althaf
> Congratulations!
Roman :-) ,
did it work over there ? ;-)
i'm actually waiting for someone to test run it , have you tried it yet?
Roman Ignatov
> i'm actually waiting for someone to test run it , have you tried it yet?
I will test it and will write to you on email! :)
Althaf k Backer
3.1.6 it doesn't seems to work well,it has some
problem communicating with DS.
Al Pech
with 3.1.5 and report the results.
-Al Pech
dz...@pochta.ru
I think that is good reason for release of Minix3 on new iso for test it.
http://code.google.com/p/minix3-usbsubsystem/
Check the README and INSTALL in the tar ball.
Antoine Leca
> I think that is good reason for release of Minix3 on new iso for test it.
Please read the full thread: the package released (which is alpha
software) works with 3.1.5, but does not work cleanly with 3.1.6, which
is the last "stable" release. I expect problems with -current too (of
course, beyond the obvious conversion of <ibm/ to <machine/ or <i386/)
> http://code.google.com/p/minix3-usbsubsystem/
> Check the README and INSTALL in the tar ball.
Furthermore, there is a potential license clash: this package (which
I understand is derived from Linux' stack) is GPLv3-licensed, and the VU
policy until now has been to avoid that license in the main tree.
Of course there is no problem to release a GPL-ed derivate of
Minix-with-USB, but I am not sure VU wants to have her name associated
with such an initiative, since it could raise communication concerns.
My �.01
Antoine
Althaf
Main reason is http://wiki.minix3.org/en/DevelopersGuide/SEF from what i
understand was introduced in 3.1.6.
AntoineLeca
> http://code.google.com/p/minix3-usbsubsystem/
> Check the README and INSTALL in the tar ball.
Great work, congratulations.
I saw the remarks about incompatibilities with 3.1.6; this reminds me
we really need to enhance the great documentation that Neil did a few
month ago, to SEF and any other stuff. It would have been a good idea
to keep the wiki up-to-date when the change was made into the trunk
(5786, 5861), but I have no idea why this had not been possible. I
also notice this happened again on March 17th, with revision 6441
which has an extensive changelog --more than 1 printed page long-- but
not much is creeping into the wiki).
I have an idea of the changes involved (well, not the last one), since
it took me by surprise when I was developing some network driver and I
saw the change while monitorizing trunk; but since I was not able to
switch away from pre-VM on the computer I was working (without
network...), I was not able to create a version which was able to
track both the tree and remains backwards compatible (compare with the
safecopies, where I do have a version which is 3.1.2 compatible, ie no
safecopies); as a result (and also because I lost access to one of the
test computers), I dropped the driver; this is the sad consequence of
dropping backward compatibility, IMHO.
Anyway, since my working computer is running 3.1.7 but does not have
UHCI, I switched to another one having network AND UHCI; it is running
3.1.3a at the moment (the other releases are in unstable state,
because of the above state of affairs); I downloaded the package, but
I quickly saw I won't go very far:
cannot include <sys/vm_i386.h>
cannot include <sys/mman.h>
implicit declaration of funciton munmap
Look like 3.1.5, and no other release, is really required... until the
USB package is upgraded to at least 3.1.6 and basic SEF support; and
it is probably better to try to match revision 6441 as well...
Antoine
Althaf
> On 17 mar, 19:31, Althaf k Backer <althafkbac...@gmail.com> wrote:
>> http://code.google.com/p/minix3-usbsubsystem/
>> Check the README and INSTALL in the tar ball.
>
> Great work, congratulations.
>
Thank you Antoine :-)
> I saw the remarks about incompatibilities with 3.1.6; this reminds me
> we really need to enhance the great documentation that Neil did a few
> month ago, to SEF and any other stuff. It would have been a good idea
> to keep the wiki up-to-date when the change was made into the trunk
> (5786, 5861), but I have no idea why this had not been possible. I
> also notice this happened again on March 17th, with revision 6441
> which has an extensive changelog --more than 1 printed page long-- but
> not much is creeping into the wiki).
Well i think problem was i didn't keep up with the new release , by the
time my deadline was up, the project was almost done with 3.1.5
which was the stable release from the commencement of this project.
> I have an idea of the changes involved (well, not the last one), since
> it took me by surprise when I was developing some network driver and I
> saw the change while monitorizing trunk; but since I was not able to
> switch away from pre-VM on the computer I was working (without
> network...), I was not able to create a version which was able to
> track both the tree and remains backwards compatible (compare with the
> safecopies, where I do have a version which is 3.1.2 compatible, ie no
> safecopies); as a result (and also because I lost access to one of the
> test computers), I dropped the driver; this is the sad consequence of
> dropping backward compatibility, IMHO.
Yes indeed , my design entirely depend of endpoint numbers of the
process for internal IPC , i have not been into the depth to situation ,
but on the surface what i can say is Data Store part has some problem
which is actually breaking it.
> Anyway, since my working computer is running 3.1.7 but does not have
> UHCI, I switched to another one having network AND UHCI; it is running
> 3.1.3a at the moment (the other releases are in unstable state,
> because of the above state of affairs); I downloaded the package, but
> I quickly saw I won't go very far:
> cannot include <sys/vm_i386.h>
> cannot include <sys/mman.h>
> implicit declaration of funciton munmap
> Look like 3.1.5, and no other release, is really required... until the
> USB package is upgraded to at least 3.1.6 and basic SEF support; and
> it is probably better to try to match revision 6441 as well...
Yes i'll be working on that :-) ,i'd really appreciate if you could bring about
the changes for SEF, from what i understand its not hard , just the
initialization
part ,to be honest i'm really off the project for few weeks ( relaxing
my head :P).
3.1.5 to more specific svn5612 which is a stable release , is the only version
i have tested the code with plus i'm not sure about it working on real hardware,
hardware emulation (qemu) and real hardware is completely different matter.
> Antoine
If you have time would you please test run it on Qemu 0.11.1 or later and 3.1.5
i haven't received any result of test running :-(. Main reason would be people
should have switched to version >= 3.1.6.
--
Althaf K Backer
http://code.google.com/p/minix3-usbsubsystem/
http://mykeystrokes.blogspot.com
Al Pech
the SHOW_ALL_DESC flag to '1' (so that I can see all the descriptors
of the USB device I attach) and it worked under 3.1.5!! I didn't test
the keyboard and mouse driver because I don't have a Keyboard or Mouse
USB device at hand.
I connected a Kingston Pen Drive and my Motorola Cellphone and I was
able to see their descriptors with no problems!
Good job Althaf.
I'll work on porting it to 3.1.6 (I have a lot of reading to do)
-Al Pech
Althaf
> able to see their descriptors with no problems!
>
> Good job Althaf.
>
> I'll work on porting it to 3.1.6 (I have a lot of reading to do)
>
> -Al Pech
:-) , well if you weren't able to see the entire listing (as Minix doesn't have
scrolling support ) do this ( qemu assumed)
ssh -pPortno user@localhost tail -f /var/log/messages
so that will show contents of that file when ever changes are made.
Thank you for testing it out , i'm really happy to see that working
over there.
Antoine Leca
> :-) , well if you weren't able to see the entire listing (as Minix doesn't have
> scrolling support ) do this ( qemu assumed)
>
> ssh -pPortno user@localhost tail -f /var/log/messages
Something is wrong with
# more /var/log/messages
?
Antoine
Althaf
> # more /var/log/messages
No , but that is not the desired result i'm expecting
from using 'more' , from what i suggested we could
see updates real time (as and when it happens),
technically with some delay.
Well,'more' is something like static display while
'tail -f' is dynamic.
Try it out ;-)
tota
Thanks.
ToTa
Althaf
there was a minix version gap during the development of this stack,
which requires porting of the
current code to the new minix version, currently i'm bit occupied with
my exams,however AI Peach and one more student from russia are working
on porting the code.
I hope that would be the aim of next release, if you are too much
interested in the usb part of minix, i would like to point out that
there is currently a heavy development done by 'Vogt, Dirk' which
aims at porting DDkit to minix supporting the USB stack from Linux and
*BSDs.
Regards
Althaf K Backer
Althaf k Backer
Well, this report contains good introduction to USB basics and the
stack design,please note the this is not the final report and may
contains spelling and grammatical errors.
http://minix3-usbsubsystem.googlecode.com/files/Project-Report-Draft-%28pdf%29.tar.bz2
Siddu
Hi Althaf,
I spent some time with the document and understood well .....
When i put some logs in the code and tried to run , its deviating from my understanding .
As per my understanding for every send in src process , there will be a corresponding receive in dst process
and until the receive happens in the dst the src process may be blocked
but the below logs show something else
in the function uhci_msg_usbd it almost sent 3 msgs but theres been no corresponding receive in the dst (usbd) process ?
Apr 26 12:26:23 10 kernel: usbd: got a message
Apr 26 12:26:23 10 kernel:
Apr 26 12:26:23 10 kernel: usbd: on new device found
Apr 26 12:26:23 10 kernel:
Apr 26 12:26:23 10 kernel: usbd: ENTER: usbd_event_new_device
Apr 26 12:26:23 10 kernel:
Apr 26 12:26:23 10 kernel: uhci-hcd: control xfer complete
Apr 26 12:26:23 10 kernel: uhci-hcd: sending message ..
Apr 26 12:26:23 10 kernel: uhci-hcd: message send..
Apr 26 12:26:23 10 kernel: uhci-hcd: control xfer complete
Apr 26 12:26:23 10 kernel: uhci-hcd: sending message ..
Apr 26 12:26:23 10 kernel: uhci-hcd: message send..
Apr 26 12:26:23 10 kernel: uhci-hcd: control xfer complete
Apr 26 12:26:23 10 kernel: uhci-hcd: sending message ..
Apr 26 12:26:23 10 kernel: uhci-hcd: message send..
Apr 26 12:26:23 10 kernel: uhci-hcd: control xfer complete
Apr 26 12:26:23 10 kernel: uhci-hcd: sending message ..
Apr 26 12:26:23 10 kernel: uhci-hcd: message send..
Apr 26 12:26:23 10 kernel: usbd: Bus:0 Port:2 Device:1 ID 0x0951:0x1607 attached
> also looking forward for the design :Phttp://minix3-usbsubsystem.googlecode.com/files/Project-Report-Draft-%28pdf%29.tar.bz2
--
--
Regards,
~Sid~
A little bird which escaped the nest had to fall before it learnt to fly !
crspybits
install and first had to do a make in /usr/src/drivers and then all
went OK. In /var/log/messages, I get:
"uhci-hcd: unable to find any uhci host controllers".
Seemingly I have to work under Qemu or get myself a USB host
controller that will work with your driver. I have a USB host
controller on the computer I'm using but seems not to be UHCI
compatible.
Chris.
On Apr 22, 3:53 am, Althaf <althafkbac...@gmail.com> wrote:
> Tota :) happy to see your interest in this project, unfortunately
> there was a minix version gap during the development of this stack,
> which requires porting of the
> current code to the new minix version, currently i'm bit occupied with
> my exams,however AI Peach and one more student from russia are working
> on porting the code.
>
> I hope that would be the aim of next release, if you are too much
>
> Regards
> Althaf K Backer
>
>
> > When will be a new version?
> > Thanks.
>
> > ToTa
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "minix3" group.
> > To post to this group, send email to min...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > minix3+un...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/minix3?hl=en.
>
> --
> --
> You received this message because you are subscribed to the Google Groups "minix3" group.
> To post to this group, send email to min...@googlegroups.com.
> To unsubscribe from this group, send email to minix3+un...@googlegroups.com.
> For more options, visit this group athttp://groups.google.com/group/minix3?hl=en.
Althaf
> That's great to see your work on USB For Minix 3! I just tried to
> install and first had to do a make in /usr/src/drivers and then all
> went OK. In /var/log/messages, I get:
>
> "uhci-hcd: unable to find any uhci host controllers".
>
> Seemingly I have to work under Qemu or get myself a USB host
> controller that will work with your driver. I have a USB host
> controller on the computer I'm using but seems not to be UHCI
> compatible.
>
> Chris.
Please understand that using qemu to develop drivers
for real hardware is different from developing driver on the real
one, there are may factors to be considered when we play with
real hardware, i haven't tested the code on real UHCI host controller,
its sure to have issues and some quirks have to applied ,
If you don't mind it would be nice, if you debug the code on real hw and
send me a patch, btw its no fun playing with UHCI :-)
crspybits
It lists from the seller as: "USB4PORT-PCI -- VIA VT6212L 4+1 Port USB
2.0 PCI", but it apparently supports UHCI.
Booted into Linux, the lshw command indicates the following
configuration:
VIA, VT82xxxxx UHCI USB 1.1 Controller VID=1106, DID: 3038).
I edited uhci-hcd.c a little to put in the VID/DID and also edited /
etc/drivers.conf to add this VID/DID. I'm remotely connected into this
system from home, and can't type on a keyboard there, but at least no
obvious errors so far. See below.
I'd like to help out with the Minix 3 USB stack development. Al Pech
and Vogt, Dirk were doing some work. How is that going?
Cheers,
Chris.
May 17 15:38:22 minix kernel: usbd: started
May 17 15:38:22 minix kernel:
May 17 15:38:22 minix kernel: usbd: USB Stack 0.01-alpha(17032010)
May 17 15:38:22 minix kernel: usbd: Copyright (C) 2010 Althaf K Backer
<althaf...@gmail.com>
May 17 15:38:22 minix kernel: usbd: License GPLv3+: GNU GPL version 3
or later
May 17 15:38:22 minix kernel: usbd: This is free software: you are
free to change and redistribute
May 17 15:38:47 minix kernel:
May 17 15:38:47 minix kernel: uhci-hcd: started
May 17 15:38:47 minix kernel: uhci-hcd: VT83C572 PCI USB Controller
(1106:3038) at 1.9.0
May 17 15:38:47 minix kernel:
May 17 15:38:47 minix kernel: usbd: Host controller driver 13745825
registered
May 17 15:38:47 minix kernel: uhci-hcd: registered with usbd
May 17 15:39:00 minix kernel:
May 17 15:39:00 minix kernel: uhci-hcd: the interrupt was not for us
May 17 15:39:00 minix last message repeated 3 times
<snip>
May 17 15:40:29 minix kernel: usbd: Device driver 13526481 registered
May 17 15:40:30 minix kernel:
May 17 15:40:30 minix kernel: uhci-hcd: the interrupt was not for us
May 17 15:40:30 minix last message repeated 3 times
May 17 15:41:00 minix kernel:
May 17 15:41:00 minix kernel: uhci-hcd: the interrupt was not for us
May 17 15:41:00 minix kernel: uhci-hcd: the interrupt was not for us
May 17 15:41:31 minix kernel:
May 17 15:41:31 minix kernel: usbd: Device driver 13745831 registered
On Apr 29, 10:22 pm, Althaf <althafkbac...@gmail.com> wrote:
> On 28 April 2010 20:23, crspybits <crspyb...@gmail.com> wrote:
>
> > That's great to see your work onUSBFor Minix 3! I just tried to
> > went OK. In /var/log/messages, I get:
>
> > "uhci-hcd: unable to find any uhci host controllers".
>
> > Seemingly I have to work under Qemu or get myself aUSBhost
> > controller that will work with your driver. I have aUSBhost
> > controller on the computer I'm using but seems not to be UHCI
> > compatible.
>
> > Chris.
>
> Hello Chris,
> Please understand that using qemu to develop drivers
> for real hardware is different from developing driver on the real
> one, there are may factors to be considered when we play with
> real hardware, i haven't tested the code on real UHCI host controller,
> its sure to have issues and some quirks have to applied ,
>
> If you don't mind it would be nice, if you debug the code on real hw and
> send me a patch, btw its no fun playing with UHCI :-)
>
> --
Althaf
Please note that
i'm currently out of station, so the support reply might be delayed.
Regards
Siddu
I've now got a UHCI board.
It lists from the seller as: "USB4PORT-PCI -- VIA VT6212L 4+1 Port USB
2.0 PCI", but it apparently supports UHCI.
Booted into Linux, the lshw command indicates the following
configuration:
VIA, VT82xxxxx UHCI USB 1.1 Controller VID=1106, DID: 3038).
Hi Chris,
I have 4 USB UHCI Controllers and 1 USB EHCI Controllers which are built within the mother board which is what i found out when i did lshw
but they dont seem to show VID/DID. May i know what's the reason ?
I edited uhci-hcd.c a little to put in the VID/DID and also edited /
etc/drivers.conf to add this VID/DID.
So in case if i have to do this what values should i feed ? Please let me know
--
Regards,
~Sid~
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gazing through the window at the world outside,
Wondering will mother earth survive ?
Hoping that the mankind will stop abusing her
Sometime !
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -