Re: VGA external on OLPC
On Tue, May 13, 2008 at 11:17 AM, Frank Ch. Eigler [EMAIL PROTECTED] wrote: Jim Gettys [EMAIL PROTECTED] writes: Note there are USB display adapters (I have one in my hand as I write this); I'd love to see someone working on X.org drivers for it. [...] The sisusb-based USB display adapters have both kernel and x.org drivers today. Yes, I bought one of these and tried to get it going. I couldn't find any reason why it shouldn't work with the standard drivers, but the whole process of simply trying to get the drivers from the standard tree compiled and on my XO wore out my patience. Putting the right drivers (usb2vga and a couple dependencies, iirc) in a XO kernel package would be a big help. --Tom ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: VGA external on OLPC
On Tue, May 13, 2008 at 8:27 AM, Bert Freudenberg [EMAIL PROTECTED] wrote: Did you try the binaries? http://wiki.laptop.org/go/Remote_display#Binaries Ah, well, I guess someone has been working on this since the last time I looked at it ;-) --Tom ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: CIPA done
On Wed, May 7, 2008 at 4:24 PM, Joshua N Pritikin [EMAIL PROTECTED] wrote: I believe we MUST error on the conservative side, especially for American deployments. If you're sending home user modifiable wifi-capable computers with kids, you're already a long way from the conservative side of the issue in the US. Playing it safe, in this case, means pretty much dropping the entire project. --Tom ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: on Sugar
On Thu, Apr 24, 2008 at 9:44 AM, Aaron Konstam [EMAIL PROTECTED] wrote: This is fine except for one thing. Running Sugar on top of proprietary software means that sugar developers who have to deal with problems in the interface between XP , let us say, and sugar will have to know alot more about the XP side of the interface than MS$ normally reveals. Why? I've written many Python applications on Linux that also happen to work on Windows. --Tom ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Walter leaving and shift to XP.
On Wed, Apr 23, 2008 at 5:40 PM, Edward Cherlin [EMAIL PROTECTED] wrote: On Wed, Apr 23, 2008 at 1:27 AM, Torello Querci [EMAIL PROTECTED] wrote: If is possible to use normal windows application on top Sugar+Windows the educational project is broken because the developers what need to write a program (program not activity) write it on windows because in this manner one PC with windows can run it, and XO XPzed too so why write code for sugar? In this scenario Sugar is dead and OLPC became a Laptop organization If Sugar cannot offer any advantages to developers writing applications for children beyond those already offered by Windows XP, it will fail regardless. Sugar would not die, and will not die. If necessary, the community will walk away from OLPC to start a new organization, and fork all of the software. We would replicate git, Trac, lists, and Pootle, all of which are under Free licenses. This has happened many times in the FOSS development world. People at OLPC have been there and done that, and in several cases gotten the t-shirt. For what it is worth, I think Edward is overstating the likelihood that a fork may be necessary in the future, and understating its potential cost. The process of porting Sugar to Windows would mostly be made up of writing Windows implementations of relatively low level libraries used by Sugar. Many of these ports, like GTK, already exist and are relatively mature. And they're open source. There is even an extant project to port DBus to Windows already. Forks are expensive and inefficient, and undertaken only when all else fails. I've read nothing to indicate that might be necessary in the future. Sugar will always be free software, even if it is sometimes running on unfree software through a compatibility layer. Given that this would make Sugar accessible to millions of children around the world already using Windows, I can't see how this would be a bad thing. On the other hand, I can't see how either OLPC or Microsoft has much motivation to invest in the port at this point. --Tom ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Rebuilding the Kernel
OK, not quite there... I installed the regular, devel and src RPM's for the kernel I've got on my XO. cd'ed to here: /usr/src/kernels/2.6.22-20080118.2.olpc.a985ba6d19d39cc-i586/drivers/usb/misc/sisusbvga Did: make -C /lib/modules/2.6.22-20080118.2.olpc.a985ba6d19d39cc/build/ SUBDIRS=`pwd` modules The result was an apparently empty file called Module.symvers Didn't seem to get a .ko Here's the Makefile: obj-$(CONFIG_USB_SISUSBVGA) += sisusbvga.o sisusbvga-objs := sisusb.o sisusb_init.o sisusb_con.o Thanks! Hope I'm not being too clueless here... --Tom On Jan 23, 2008 12:11 PM, Dan Williams [EMAIL PROTECTED] wrote: On Wed, 2008-01-23 at 12:01 -0500, Tom Hoffman wrote: Thanks Dan. I'll give this a shot. No problem, does the usb2vga stuff give you a Makefile at all? If so, could you attach it? If not, it's pretty easy to make one, assuming that the module doesn't require weird build-time magic (most don't since they are 10 files and usually just one or two). Dan --Tom On Jan 23, 2008 11:42 AM, Dan Williams [EMAIL PROTECTED] wrote: On Wed, 2008-01-23 at 11:24 -0500, Tom Hoffman wrote: Hi all, I'm trying to get a USB2VGA adapter working. Step 1 would appear to be compiling the SISUSBVGA module in the standard kernel tree and getting it onto my XO. So I've been trying http://wiki.laptop.org/go/Rebuilding_OLPC_kernel And rpmbuild bombs out the same way whether I use a SRPM or git: ++ /usr/bin/id -u + '[' 500 = 0 ']' + /bin/chmod -Rf a+rX,u+w,g-w,o-w . + mv linux-2.6. vanilla mv: cannot stat `linux-2.6.': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.57150 (%prep) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.57150 (%prep) This is on Fedora 8. Anyone have any helpful advice? I'll update the wiki if you do. You don't need to rebuild the kernel itself. All you need is to install the kernel-devel package for the kernel you want to build against. Then cd into your usb2vga driver directory. Run: make -C /lib/modules/kernel version/build SUBDIRS=`pwd` modules And it'll spit out a .ko you can load if usb2vga has a makefile in the appropriate form (which should be quite simple). If you want to build it for the XO, find out the version of the kernel running on the XO, and get the matching kernel-devel package from Andres' site at http://dev.laptop.org/~dilinger/stable/ And do the same: make -C /lib/modules/olpc kernel version/build SUBDIRS=`pwd` modules Many times, the module (like madwifi, some out-of-tree v4l2 drivers, or others) will include the right makefile magic for you to just type 'make' and it'll handle this all for you. Dan ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
