Re: Native port for Raspberry Pi [Development (General)]

Forum Index

Board index » Development » Development (General) » Native port for Raspberry Pi

Browsing this Thread: 1 Anonymous Users

Bottom

Previous Topic

Next Topic Register To Post

« 1 (2) 3 4 5 ... 13 »

mt12345

Re: Native port for Raspberry Pi

#113

Home away from home

I think it isn't case for ARM simply because there are not many apps compiled for it.

Posted on: 2013/6/16 21:32

phoenixkonsole

Re: Native port for Raspberry Pi

#112

Home away from home

Where is the difference between ABI v1 (x86) and ABI v1 (ARM)

I mean if I would ask to ditch ABI v0 on x86 everyone will tell that ABI v1 is still "in the flow" - i mean it may get changes which will always break compatibility to compiled apps.

If this isn't the case for ARM why it is for x86? Or have times changed and we reach the finish line for ABI v1?

Posted on: 2013/6/16 21:15

www.aeros-os.org AEROS for Raspberry Pi
www.aros-broadway.de Native AROS for i386 and m68k
www.indiego-Gaming.com indieGO! The AppStore for all amigans
www.ares-shop.eu

magorium

Re: Native port for Raspberry Pi

#111

Home away from home

@phoenixkonsole:
For now abiv1, so that should be your target.

Although Kalamatee would really be the one to give a truthworthy answer, i don't believe he ever targeted v0 (or ever will).

Posted on: 2013/6/16 18:59

phoenixkonsole

Re: Native port for Raspberry Pi

#110

Home away from home

Hi,

will AROS ABI v1 or v0 or both be available for the Pi?
I need to now what I should target. I assume ABI v0 armhf. ???
I would like to convince people to do some ports of apps and games.

Posted on: 2013/6/16 18:43

www.aeros-os.org AEROS for Raspberry Pi
www.aros-broadway.de Native AROS for i386 and m68k
www.indiego-Gaming.com indieGO! The AppStore for all amigans
www.ares-shop.eu

bloodline

Re: Native port for Raspberry Pi

#109

Home away from home

Quote:

Kalamatee wrote:
Quote:

bloodline wrote:
Quote:

Kalamatee wrote:
Quote:

bloodline wrote:
Good luck with the USB, I'm afraid I have no ability to assist with the USB... I might be able to help a bit with graphics acceleration though :-/

I will probably try and write a simple driver to allow access to the GPIO first :)

GPIO shouldn't be too bad but bear in mind it is already accessed in places so they would need to allocate pins etc through it (e.g. sdcard to flicker the activity light, serial debug to output data on the GPIO pins)

Ive also started an i2c driver that will need to allocate GPIO pins. Feel free to work on it if you are interested ;p

To improve the Gfx driver, we will need a DMA resource implemented that it and other drivers (e.g. sdcard) can use to perform dma operations. The Gfx driver will need this to perform blits.

I've done some bear metal programming on the pi, where I treat it as a microcontroler, so I understand how the GPIO is set up on the board... The difficulty for me will be writing an exec style Device as I've never done that before :)

A ".device" might be overkill for the GPIO needs - probably a ".resource" would be a better fit.

I never really understood what a resource was... a library without functions? I think Jason summed up the difference between libraries, devices and resources on the dev list...

Anyway my build keeps crapping out at .../workbench/libs/popupmenu/... no idea why :(

Posted on: 2013/6/13 21:07

http://www.troubled-mind.co.uk/

Kalamatee

Re: Native port for Raspberry Pi

#108

Home away from home

Quote:

bloodline wrote:
Quote:

Kalamatee wrote:
Quote:

bloodline wrote:
Good luck with the USB, I'm afraid I have no ability to assist with the USB... I might be able to help a bit with graphics acceleration though :-/

I will probably try and write a simple driver to allow access to the GPIO first :)

GPIO shouldn't be too bad but bear in mind it is already accessed in places so they would need to allocate pins etc through it (e.g. sdcard to flicker the activity light, serial debug to output data on the GPIO pins)

Ive also started an i2c driver that will need to allocate GPIO pins. Feel free to work on it if you are interested ;p

To improve the Gfx driver, we will need a DMA resource implemented that it and other drivers (e.g. sdcard) can use to perform dma operations. The Gfx driver will need this to perform blits.

I've done some bear metal programming on the pi, where I treat it as a microcontroler, so I understand how the GPIO is set up on the board... The difficulty for me will be writing an exec style Device as I've never done that before :)

A ".device" might be overkill for the GPIO needs - probably a ".resource" would be a better fit.

Posted on: 2013/6/2 0:00

bloodline

Re: Native port for Raspberry Pi

#107

Home away from home

Quote:

Kalamatee wrote:
Quote:

bloodline wrote:
Good luck with the USB, I'm afraid I have no ability to assist with the USB... I might be able to help a bit with graphics acceleration though :-/

I will probably try and write a simple driver to allow access to the GPIO first :)

GPIO shouldn't be too bad but bear in mind it is already accessed in places so they would need to allocate pins etc through it (e.g. sdcard to flicker the activity light, serial debug to output data on the GPIO pins)

Ive also started an i2c driver that will need to allocate GPIO pins. Feel free to work on it if you are interested ;p

To improve the Gfx driver, we will need a DMA resource implemented that it and other drivers (e.g. sdcard) can use to perform dma operations. The Gfx driver will need this to perform blits.

I've done some bear metal programming on the pi, where I treat it as a microcontroler, so I understand how the GPIO is set up on the board... The difficulty for me will be writing an exec style Device as I've never done that before :)

Posted on: 2013/6/1 23:27

http://www.troubled-mind.co.uk/

Kalamatee

Re: Native port for Raspberry Pi

#106

Home away from home

Quote:

jman wrote:
@kalamatee, bloodline

Just out of curiosity, when you mention the USB driver, you mean porting the Poiseidon USB stack or writing one from scratch (please excuse my ignorance)?

Implementing the hardware driver that Poseidon uses to interact with the USB components.

Posted on: 2013/6/1 10:52

Kalamatee

Re: Native port for Raspberry Pi

#105

Home away from home

Quote:

bloodline wrote:
Good luck with the USB, I'm afraid I have no ability to assist with the USB... I might be able to help a bit with graphics acceleration though :-/

I will probably try and write a simple driver to allow access to the GPIO first :)

GPIO shouldn't be too bad but bear in mind it is already accessed in places so they would need to allocate pins etc through it (e.g. sdcard to flicker the activity light, serial debug to output data on the GPIO pins)

Ive also started an i2c driver that will need to allocate GPIO pins. Feel free to work on it if you are interested ;p

To improve the Gfx driver, we will need a DMA resource implemented that it and other drivers (e.g. sdcard) can use to perform dma operations. The Gfx driver will need this to perform blits.

Posted on: 2013/6/1 10:49

jman

Re: Native port for Raspberry Pi

#104

Home away from home

@kalamatee, bloodline

Just out of curiosity, when you mention the USB driver, you mean porting the Poiseidon USB stack or writing one from scratch (please excuse my ignorance)?

Posted on: 2013/6/1 10:38