.
Annunci online

All that comes in the mind of an italian guy moved to california
2 novembre 2010
Technologies: AROS: Closing the loop

What is this? Read and see....

After at least three failed attempts (Evilrich and then Tigger, disappeared almost immediately,Greg 'bheron' Casamento - that had a good amount of bad luck and, very shortly, Gary 'Gaz' Pearman), finally the Kickstart integration bounty started to deliver results and code.

The latest person to get the task is called Jason McMullan; this time he started to submit patches for 68k ROM in the developers mailing list around the begin of october. In october 6, deadwood asked him what he was working on, and he answered:


Frankly, I'm attempting KickStart Replacement Bounty I and II.

I'm working on porting AROS to the Commodore Amiga 1200, specifically
the UAE emulation. I also have a real A1200 I would like to get
this running on, but I'll need a flash burner for that.

I have a ROM image building with stock ELF binutils 2.20 and gcc 4.5.1,
with (I think) the correct register based ABI for libcalls. Total
ROM size is currently ~430K, so I should have plenty of space for the
Amiga AGA/OCS/ECS HIDDs and whatever other device drivers I need to write.

My short term goal is to get all the 'support' patches into the mainline
first, then bring in the m68k-amiga specific code, so that I have a
working build when I check in the m68k-amiga support.

I plan to complete this goal withing the next few weeks, depending on
how badly my changes clash with the existing architectures. I have
tried to be clean with this, but accidents happen.

My medium term goal is to boot an AROS Workbench disk, and have all
the AROS/C applications work on A1200 on UAE.

I hope to complete *that* goal by December 31, 2010.

( No HUNK support, it's all ELF right now, but HUNK backwards compatibility
  should be doable in the future.)

My long term goal is to be able to boot a Amiga WorkBench 3.1 disk, and
have all the Amiga HUNK apps work. This would allow AROS-m68k-amiga to
fully operate as a KickStart replacement ROM.



Jason did not simply applied for the bounty: he worked on a proof of concept  achieving, thanks to the latest UAE developments that finally allowed amiga UNIX buiilds to run, the build of a debian image to be used for compiling AROS on 68k. From this point he begun to submit a big amount of patches for getting the AROS 68k version back on track using GCC 4.5.0.

Its plan is to first be able to compile AROS then, slowly, replace in ROM images original amiga libraries with AROS ones in order to obtain a bootable AROS rom; furthermore Jason thinks to include, together with AROS ELF file format, also Amiga Hunk format in order to obtain the binary compatibility with Amiga software.

Lately Jason is no more alone in working in the bounty, even Toni Wilen, one of the WinUAE team coders, started to work on the bounty helping Jason in setting up the rom, especially taking care of the amiga-only hardware device drivers; he announced its intention to help Jason in this letter in the developer mailing list on October 21st:


Hello, it is WinUAE guy here. I think it is time to finally post something
here now that m68k build is really happening (great job!)

Sooner or later I am going to start working with 68k rom, mainly for (game)
emulation use, including add/fix missing Amiga specific drivers (I know
Amiga custom hardware inside out and also how drivers work) Unless someone
else have already started writing boring driver code..

I can help with low level drivers like Amiga floppy hardware driver, display
(+copper/blitter), CIA+keyboard, mouse etc.. anything that is close to
hardware and needed to boot not-too-badly programmed disk based games
without need for original rom. Of course many really old games will never
work without some kind of KS1.3 "compatibility" mode but that isn't
important now, perhaps someday..

Any list(s) of missing/not yet working 68k specific device drivers?

I think there are 2 phases:

Phase 1: support programs that have custom bootblock, possibly loads few
more tracks using trackdisk.device and then the rest uses hardware banging
loader.
Phase 2: support programs that boot to CLI, uses startup-sequence.

btw, I don't care about the bounty (or about "new" Amigas), I "only" want to
finally have (win)uae with built-in legal more or less "retro-compatible"
rom replacement.


Before to go on, is better to remind: Why the Kickstart integration phase 1 and 2 are so important?

The integration bounty are important for a good serie of reasons: first of all, once the AROS 68k port will be completed, it also will include binary compatibility with the HUNK file format, and most of the existing amiga applications written according to the Amiga OS guidelines will work directly on AROS: that means is possible to use AROS in place of the original Amiga OS; unlike the original Amiga OS 3.x, AROS is actively developed and therefore there is the advantage of having new features and patches;

second, AROS is open source and free of charge, and a 68k version b inary compatible with Amiga programs will come out handy for all those alternate and homebrew projects that require Amiga OS compatibility without the need of an official Amiga ROM, names as Natami, UAE/WinUAE.J-UAE, Minimig and the FPGA Toaster-on-a-chip comes to mind;

third but not less important, the existence of an Amiga version of AROS has an emotional factor, binding to the original Amiga Replacement OS project of AAron Digulla - sort of the return home (Amiga Hardware) of the Prodigal Son (AROS) and will add even more legitimacy to the project form those people that so far were against AROS for the fact that does not run on Amiga Hardware; potentially can also add for some more developers that might decide in contribute for improve the compatibility and the performance, just as Tony Wilen did.

Today November second, Jason communicated another significant progress:

I have successfully loaded my first disk block using Frankenrom with KS 3.0!
With Toni's help, I realized that I needed to enable DMA (DUH!) early on after IRQs have been enabled, and KS 3.0 + AROS exec will now get to the point where it *sucessfully* loads the first disk block.
However, the screen is still black. Is any of this debugging useful? (I disabled alert.hook and exec/SetFunction() Just In Case, but no change in behaviour)


And today even better:

KS 3.0: Getting there! exec will now get to the boot screen! http://www.evillabs.net/wiki/index.php/AROS_m68k-amiga
I need to make a disk with *just* the Install boot block now.

and the result is the boot image seen above; it is just AROS exec and the rest is Amiga routines but is a significant step forward!

Jason recommmended Tony Wilen for the assignment of the Phase 2 of the bounty since he has more experience in the Amiga OS hardware internals and is able to code effectively drivers. The outcome of this bounty are keeping mu attention level high nd am really excited to see the progresses!

TECNOLOGIE
19 marzo 2009
Diary: Technologies: AROS: on SCALE, iMica and OWB Beta

The Westin Hotel in Century Boulevard, where SCALE was held

Sunday February 22nd, despite is already noon the sky is cloudy, with all the clouds getting flat on the low quota high pressure in a sort of whitish steamy ceiling over the city of Los Angeles.

My wife drops me in front of the Westin Hotel's parking lot in Century Boulevard, better known from LA people as the "Hotel Strip" just above LAX then she starts the car and head towards north. Carrying my two bags -one of which is my laptop- i too start to walk towards the hotel main door excited.

Despite the opening might be good for some family drama, i am just talking about my arrive at SCALE (Soutern CAlifornia Linux Expo) for my AROS intervention, listed under the Open Source for Beginners section; i am expected to talk at 1.30 pm and have still one hour left so i go check in at the reception and they give me a speakers red badge, some promotional stuff (cloth bag, a XL american size t-shirt which i can use as a camping tent as much is oversized for me) and start walking towards the hall ehere will held my speak.

My speak is expected to last one hour only so i need to follow my script thoroughly; this is my absolute first advocacy in a convention; so far the biggest crowd I have been in front with was together with the choir I used to sing in italy as Basso chorist; we had the honor, together with other four choirs, to sing all together for the Pope in Porto Recanaty in 2005, with a crowd of around 600,000 people: too big to realize it.
Here i have not even ten people in a theatre with at least 100 places, but is different: this people is MY own crown and I am the focus of them, together with AROS that in my laptop, don't look at the best of its shape: my laptopis a DELL VOSTRO 1000 with AMD sempron, 1.5 gig of RAM, 100 gig hard disk, broadcomm wireless card, EHCI USB card (PCI\VEN_1002&DEV_4386&SUBSYS_022A1028&REV_00\3&2411E6FE&0&9D) and a Sigmatel sound card:  definitely not the most OpenSource friendly laptop but, as a take its defense, it was bought to work on it, not to advocate on it...

i tried to make it boot from the live CD and the first sensation is good: AROS seems to perform quite fast and well (despite the widescreen is not supported by my ATI card and the aspect ratio of the screen looks a bit weird) and my sound card give no signs of life; plus i was unable to set my virtual machine to get connected [now solved, but i opened at the time a topic on aros-exec here] and still did not had (yet) the OWB beta version to show. Despite that i have been able to use poorPDF as a slide projector and also to show the VmWAROS Wanderer desktop complete with Ken's icons.


Here I am in the Westin Hotel's Theatre B talking about AROS

The overall intervention lasted one hour; guess all my inexperience in doing introductions showed up - i admit it - in missing to fully follow the script that I prepared and in making the slides getting along iwth the speak, so at the end i jumped some slidesand in some cases i indulged a little longer in details rather than in the focus points; at the end i had to show the available software a bit on a rush, but i hope to have been able to transmit the enthuisiasm, my own and the community itself one, in developing and promoting the use and further development of AROS.


Well, not exactly "sold out"...

The public, those few that came, were surely with an amiga background: almost everybody knew what Amiga OS was and many of them seemed to approve the concept; there has been questions on the toolchain and about memory consumption but, in general, i am afraid that without showing adequately AROS on the run - as i haven't been able to that day - they considered the project just a small curiosity: or not? Wish to see how many contacts came to aros-exec from Southern California lately...

But guess that anyway i have been able to show the commitment and the passion of AROS supporters: if i sohuld choose a sentence to describe what I did that day guess will choose the one from Joe "Zonker" Brockheimer from its own SCALE intervention (page 16 of the enclosed PDF file): "Do something,even if it is wrong".

Beside my own intervention i had very little time to wander around the expo: my wife could not park around the place (the parking fee for the hotel was a $14 flat fee and being at the end of the month cash was tight) and was waiting for me outside the hotel doing "pings" every two minutes:P therefore i tried to do a fast tour of the main lobby and i had the luck to meet Gregory John Casamento, a.k.a. bheron, GNUStep mantainer and assigned to the Kickstart replacement bounty in its own GNUstep booth: i introduced myself as an AROS advocate and had a short talk with him about the subject: he told me that is undoubtly difficult to retrieve reference material and also old hardware as well in order to complete the bounty (material such as Rom Kernel Manuals, technical newsletters, developers kit,etc). In case you want to provide some material to Gregory you can get in touch with him through his blog or his AROS blog, the AROS developer mailing list (subscription required)  or in aros-exec.

So in short this is the essay about my SCALE partecipation. If only i had the OWB beta under my hands a couple of hours earlier probably my introduction should have been even juicy than it has been, but then my network problems with VmWAROS surely could have made it look again stuck, who knows?

By the way, the most important news of the month and fo the whole story of AROS is that finally OWB beta is here!

After the first attempt made by Robert norris on provide AROS with a modern web browser trying to convert Webkit  and that lead to the december 2007 semi-working alpha version, able to navigate but slow quirky and quite unusable comes - also thanks in part to Robert's job - the AROS port of Origin Web Browser comes bringing javascript and CSS support, along with tabbed browsing and a download manager.

To install OWB is required to have a recent AROS build (february 19 or later) or to copy the files muimaster.library and arosc.library from a recent nightly build in your libs: directory.

For VmWAROS users Paolo besser prepared an update .iso based on a newer build that contains both the new required libraries and a stacksize icon fix (before of this update assign the stack size from an icon does not work). This update has to be used together with the VmWUpdate script. The iso can be downloaded from here.

Please BE VERY CAREFUL in doing the update and follow the enclosed .pdf file: i missed to read it and simply done the upgrade as a simple VmWAROS upgrade and lost amistart, the configIP stopped working together with arosTCP and, after i made the fatal mistake to try to reinstall the old version of VmWAROS with the installer i was greeted by a sudden reboot, followed by a skinnless error requester in old topaz font  "Mountfile 'AROS:Devs/DosDrivers/PIPEFS' is invalid: wrong number of arguments" and an OK button. Pushing the OK button the system rebooted and showed the same requester again, over and over. The only viable option I found to restore the system was to boot from a recent nightly iso and install again the system. Then, in order to get the net working again had to reconfigure AROSTCP by hand; so, in case you might do a mistake like mine and you might not find the instruction to do it on net (usually in the AROS wikibooks) am going to repeat it here:


  • in ENVARC: create the AROSTCP directory;
  • go through shell inside ENVARC:AROSTCP typing ENVARC:AROSTCP; the path at the left should become like 1.AROS:Prefs/Env-Archive/ArosTCP> ;
  • type echo "true" > autorun - will create the "autorun" file that contains the value "true".
  • from sys:system/network/AORSTCP copy the directory db inside ENVARC:AROSTCP typing those instructions:
    cd ENVARC:AROSTCP
    makedir db
    copy db sys:system/network/AROSTCP/db ALL
  • still in ENVARC:AROSTCP type the command echo "env:arostcp/db" > config - that will create the file "config" inside ENVARC:AROSTCP;
  • at this point follow the same instructions used for the manual configurations in VmWAROS, edit the following files: netdb-myhost, interfaces and static-routes, and then reboot the system.


Hmm, guess is about time to restart that project of mine to configure AROSTCP made in lua...


OWB open on my italian blog

Before and after the  problem I tested OWB on VmWAROS (form the office, where the virtual machine has no issues in connecting) and also contributed on its debug; the actual veersion 0.9.2 is already out and includes some of the fixes and features requested by the users; still there are some problems in sending attachments from yahoo (the attachment does not get recognized) and in saving mails in gmail; beside that my OWB experience has been quite pleasant; despite the obvious slowliness of the Virtual Environment enhances some small glitches such as the not full asynchronicity of CURL library (that load the page components), the browser is fast, mouse wheel is fully supported, the page rendering is quite good and the user interface, although a bit basic, is clean and enjoyable. If you want to see OWB in action, nikos posted avideo on youtube. Best performances can be achieved by assigning a stack size of 1024000.

Future plans for OWB include bookmarks and history support; furthermore, some threads are already started on aros-exec to propose a phase 2 browser bounty that should provide a plug-in system and a flash player port as in example SWFDEC or GNASH; for the latter one there are some concerns due to the results of a recent static port on Haiku - where with static port is meant that all libraries and dependences were included in the binary file - and that turned out to be quite heavy: 135 megabytes...

Stanislaw also prepared a bug tracker for OWB that, after a little stay in google code, now hgas been relocated for good in sand-labs, together at the OWB download link. The description page of all work occurred in OWB,instead, is still here.

Another innovation made by Stanislaw Sszymczyk is the possibility to build AROS parts outside the source tree: in other words is now possible to compile AROS in other directories beside those supposed to be used in the source tree; this characteristic comes out handy for the development of alternate versions of applications (such as hosted, native, with or without debug output) in parallel; plus, with updated cross-compilers it is also possible to compile binaries for different processors at the same time (sam,efika,i386,i3856/64,etc.) and that allow to the developers to only run "make" to update the components without need to reconfigure everything.
So far the compilation outside the source tree can be done on few applications only due to the fact that some tools need to get required files from the source tree and that might cause problems; furthermore is not possible compile both inside and outside the source tree at the same time yet.
(Thanks to Nick "Kalamatee" Andrews for a better explaination of the function).

Recently the boot mechanism of AORS is changed: if the system is updated with a recent build it is required that the file aros.boot is present in the root of the system disk; said file needs to be copied manually form the build iso, else the system will complain about a bootable drive missing in the hard disk and will not proceed further.

Steve Jones can be an unknown name to the most of the new member of the Amiga/AROS community and for those that left Amiga as main system before 1995/96 while for the old guard members this mane is linked to the Siamese System, the system created to readdress Amiga graphical output on PC graphic boards through RTG and that was supposed to be one of the cornerstones of a PCI based Amiga system; the plug on thje project has following been pulled by Gateway and nothing came out of it.
Now Steve comes back in the AROS landscape introducing a new compact PC machine based on Intel Atom with selected hardware for the best performance under AROS, and is equipped with the latest VmWAROS distro version: the machine name is iMica (purposely reminds Amiga) and the price is quite affordable, around 250 UK pounds - around 400$. The AROS support has also been endorsed by Kalamatee efforts in provide a working network card drivers; on the sound side iMica uses for the moment a SoundBlaster Live with EMU10k chip (supported and proven working), in the hope to see more sound card drivers available in the next future; as usual, if somebody has experience in low level programming and wish to join the developers team for writing new drivers is welcome. More informations about iMica are available in the AROS Show.

Pavel "Sonic" Fedin has released a new beta of the Windows hosted AROS; despite still has problems in the refresh, also due to the way AROS actually manages themes, this new version will allow developers and users to run AROS in Windows without the need of a virtual machine.
To distribute the Windows-hosted version, Pavel resurrected the old Snapshots functionality of Aros.org; the latest version of AROS windows hosted can be downloaded here.

Michal Schulz is still going on in the Efika port of AROS; being the most of the code done, now he is focusing in optimizing the port; just the last March 9th, Michal released a new test iso downloadable here, to fix some third party MUI classes instability that caused Zune preferences to crash or not to be launched at all, and he further fixed USB stacks including a OHCI bug that brought not to update some periferals status or to retrieve some "zombie " periferals;  then ha added a new Efika port feature: a specific debug that will show precise particulars on where a program or a library crashed; in the todo list of Michal there will be also some way to prevent AROS to freeze in case of system crash in a similar fashion to the os4 Grim Reaper.

Oliver Brunner is still working at its Janus-UAE; latest features are the amiga public scerens support as AROS screens and the GTK-MUI GUI update made similar to the windows UAE in order to handle the full screen support.

Fabio "Allanon" Falcucci has recently released a pictures and thumbnails viewer made with Hollywood and that uses its own SCUI-lib routines for the user interface; the program, called LookHere, can be downloaded here.

And to finish, good news from Paolo Besser: the version 1.1 of VmWAROS is in progress; Paolo decided to increase the version number due to the new boot system and devices fix as mentioned above. The new version shows very interesting features, as the IconDress script, that allows to exchange icon sets extracting it from .ipkg archives and replacing the actual ones; new applications will be bundled such as the new ArosPDF by Craig Kiesau, the new MPlayer build and, of course OWB; and last Paolo intends to give a mahjor clean-up to the distro, removing those applications that still use the old muimaster.library which is responsible for the non functioning zune Preference panel. The removed applications list is available in this thread on Aros-exec; in the same thread Paolo ask those applications developers to recompile it linked to the latest library version so that he will add the fixed application again to the distro. The latter is particularly important for Simple Editor and for marranoFTP, especially the latter one, having no other FTP clients available on AROS.
sfoglia
  

Rubriche
Link
Cerca

Feed

Feed RSS di questo 

blog Reader
Feed ATOM di questo 

blog Atom
Resta aggiornato con i feed.

Curiosità
blog letto 1 volte

Older Posts

Who links to me?
Get in touch with Simone Bernacchia

 




IL CANNOCCHIALE