On Dec 24, 2013 2:04 AM, "APRichelieu" <[email protected]> wrote: > > Den tisdagen den 24:e december 2013 kl. 01:03:16 UTC+1 skrev Brent: > > Ok, got it. I need to contribute to try it out. Here is my problem, and I would like to hear if this solves it. I have a hub that uses the SMSC 2512 hub chip (USB2512QFN36). Mass storage devices work as long as it's inserted at power up. Any hot plugging after boot will not work. Does your kernel fix this problem? > > What I find with the standard kernel, is that if You have a hub inserted at boot time, you can hot-plug stuff using the hub. If you remove the hub then you have to reset the device. > If you have a device inserted at boot, it is detected and is functional. > If you remove it after the boot and reinsert it, it is no longer detected. > For some devices, removal will crash the kernel within a minute. > > With my patched kernel, I can remove hub and / or devices and have them be detected and functional after boot, and can do this multiple times. > Tested with a mouse, keyboard, USB Serial and Hub. > > > > > > > > > Also, I have some other items in the kernel that I need enabled. If I contribute $50 or $125 I only get whatever you built into your kernel... right? Could I give you my .config and you build it? > > My idea was $50 will get you a root file system without source.
'Without source' go read the GPL again... > $100 will get you the rootfs, and then you get an Angstrom layer which builds > the kernel with the patches after the end of the campaign. > You can start with the binary, and if you want source, chip in another $100 later, > but this will be more expensive than getting the $100 perk. > > Obviously, once someone get the source, they have every right to publish it > according to the GPL, including the right not to ship it. > I will proably do that myself at some stage, so the perks essentially buys you time. > > The $125 is my hourly rate for any extra work, so you need to select an option > above, and then an additional $125. > 1 extra hour should be sufficient for rebuilding the kernel. > > > > > > On Mon, Dec 23, 2013 at 6:33 PM, APRichelieu <[email protected]> wrote: > > > > Den måndagen den 23:e december 2013 kl. 20:26:20 UTC+1 skrev Brent: > > > > > > > Where do I go to get Ulf's kernel? I would like to test but I don't know where to look. Is there a patch somewhere that I missed? > > > > > > > > > > > > > Check The http://igg.me link in your post. > > > > > > > > > > > > > On Monday, December 9, 2013 5:57:56 PM UTC-5, > > > [email protected]: > > > > > I've also put in $125 and must say that I haven't had any troubles since using Ulf's kernel. > > > > > > > > > > Thanks Ulf > > > > > > > > > > On Monday, December 2, 2013 1:53:39 PM UTC-7, Philippe Laurent wrote: > > > > > I've ponied up for the $125 donation. Gotta have this running right. > > > > > > > > > > > > > > > > > > > > On Mon, Dec 2, 2013 at 7:23 AM, APRichelieu <[email protected]> wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Den lördagen den 31:e augusti 2013 kl. 17:42:09 UTC+2 skrev [email protected]: > > > > > > > > > > > > > > > I'm using my Beaglebone Black with a USB temperature sensor. It works very well, however I noticed monitoring stopped last night after roughly 35 days uptime. This morning I looked more closely into the log file and noticed: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > kernel: [2892926.929555] CAUTION: musb: Babble Interrupt Occurred > > > > > > > > > > > > > > > > > > > > I wasn't able to successfully reset the USB device and before I was able to restart the BBB stopped responding. I power-cycled it and it was back to normal again. Any ideas what caused this kernel message? > > > > > > > > > > > > > > > > > > > > > > > > > I set up a crowd-funding project on > > > > > > > > > > http://igg.me/at/eMagii/x/5581172 > > > > > > > > > > for people that wants to have USB host hot-plugging on the Beaglebone Black > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > For more options, visit http://beagleboard.org/discuss > > > > > > > > > > --- > > > > > > > > > > You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group. > > > > > > > > > > To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/C6gMT2_FfiM/unsubscribe. > > > > > > > > > > To unsubscribe from this group and all its topics, send an email to [email protected]. > > > > > > > > > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > > > > -- > > > > For more options, visit http://beagleboard.org/discuss > > > > --- > > > > You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group. > > > > To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/C6gMT2_FfiM/unsubscribe. > > > > To unsubscribe from this group and all its topics, send an email to [email protected]. > > > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > > > > > > > > -- > > -brent > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
