Bounty List?


11 posts
by Cycl0ne » Mon Jun 25, 2012 8:11 am
Hi,

i ordered a Raspberry Pi 2 Weeks ago and hopefully I will get one someday. While i was fiddling with all the informations posted, i was curious if there is some sort of bounty list, where one could give a bounty to someone who ports something to Raspberry Pi?

As a example, I would offer 500€ to someone who creates a platform in qemu that is 100% compatible with Raspberry Pi with all registers/the memorymap and all extension, so that all people waiting for their raspberry pi can use qemu on a one to one basis for development until their raspberry pi arrives, without hassling rewriting parts of code, because the address space is different or some parts are not in the emulation.

Just to be curious, do you think such a bounty list could help improve Raspberry PI further?
User avatar
Posts: 102
Joined: Mon Jun 25, 2012 8:03 am
by godFather89 » Mon Jun 25, 2012 8:24 am
A bounty list would be helpful in some cases.

What you want (qemu full support for RPi) is going to cost a lot more and only Broadcom can help you with that.
Posts: 150
Joined: Fri May 18, 2012 9:40 am
Location: Timisoara, RO
by adlambert » Mon Jun 25, 2012 8:55 am
Bounty list is not a bad idea, but Pi manuacture is really coming on stream now and people won't have to wait for the real thing soon.
Posts: 291
Joined: Tue Jan 03, 2012 3:18 pm
by Cycl0ne » Fri Jun 29, 2012 8:07 pm
Hmm, ok was just asking, because im a Professor at a University in Germany. I would like to offer our computer science students the possibilty to develop for arm without buying one (in the lab the real hardware, and for the homework the qemu).
User avatar
Posts: 102
Joined: Mon Jun 25, 2012 8:03 am
by AndrewS » Wed Jul 04, 2012 6:56 pm
University students can probably afford to buy their own Raspi, surely? ;)
User avatar
Posts: 3626
Joined: Sun Apr 22, 2012 4:50 pm
Location: Cambridge, UK
by joeka » Thu Jul 05, 2012 8:52 am
Just being curious: can I ask at what university you teach?
Posts: 6
Joined: Tue Jul 03, 2012 9:12 am
by AshleyC » Thu Jul 05, 2012 5:42 pm
ohh that kind of bounty list, was getting exited at the thought of taking out targets for quick cash
Posts: 26
Joined: Sat Jun 16, 2012 1:34 pm
Location: Derby
by tufty » Thu Jul 05, 2012 6:53 pm
/me looks nervously over shoulder.
Posts: 1368
Joined: Sun Sep 11, 2011 2:32 pm
by Bakul Shah » Thu Jul 05, 2012 8:27 pm
Cycl0ne wrote:As a example, I would offer 500€ to someone who creates a platform in qemu that is 100% compatible with Raspberry Pi with all registers/the memorymap and all extension, so that all people waiting for their raspberry pi can use qemu on a one to one basis for development until their raspberry pi arrives, without hassling rewriting parts of code, because the address space is different or some parts are not in the emulation.

You may want to offer this on the qemu-devel list.

One can probably provide support for GPIO and most registers but compatibility with the GPU is not feasible. May be just the framebuffer wouldn't be hard. Another problem is the binary blob (TM) is evolving rapidly -- a lot of new config.txt parameters have been added but they are not fully documented in one place.
Posts: 293
Joined: Sun Sep 25, 2011 1:25 am
by AndrewS » Sat Jul 07, 2012 2:32 am
Bakul Shah wrote:You may want to offer this on the qemu-devel list.
One can probably provide support for GPIO and most registers

When this was mentioned before, I suggested viewtopic.php?p=83832#p83832

a lot of new config.txt parameters have been added but they are not fully documented in one place.

AFAIK they should all be documented at http://elinux.org/RPi_config.txt :?:
If you find any that aren't you should probably give Dom/JamesH/Gert a nudge ;)
User avatar
Posts: 3626
Joined: Sun Apr 22, 2012 4:50 pm
Location: Cambridge, UK
by Bakul Shah » Sat Jul 07, 2012 8:38 am
AndrewS wrote:
Bakul Shah wrote:You may want to offer this on the qemu-devel list.
One can probably provide support for GPIO and most registers

When this was mentioned before, I suggested viewtopic.php?p=83832#p83832

a lot of new config.txt parameters have been added but they are not fully documented in one place.

AFAIK they should all be documented at http://elinux.org/RPi_config.txt :?:
If you find any that aren't you should probably give Dom/JamesH/Gert a nudge ;)

Thanks. I was forgetting that page as I hadn't looked at it in a while. The missing ones I noticed:

device_tree (default bcm2835.dtb?)
kernel_old (is this still valid?)

There may be more. Scraping Dom's replies for "=" might yield a complete list : )

It would make sense to put *all* the variables in something like /boot/default/config.txt as a reference, with everything commented out as in

# var=defaultvalue

I can create an initial version if there is interest.

PS: good suggestion re: cloning code from existing gpio panel code from another project!
Posts: 293
Joined: Sun Sep 25, 2011 1:25 am