2 Merko:
Here is what i can do now:
- DV camera support.
- If my FireWire PCI card is working, IP-over-1394 support.
- MUI GUI (at least status display, the whole thing is very plug-n-play so i don't know if there'll be anything to configure).
There are also the following things which i can't support because i have no hardware:
- Video1394 - devices sending high-quality uncompressed video. These are some professional equipment, NOT a regular DV camera.
- AMDTP - this handles some professional audio equipment. Linux support is limited to audio playback only.
- sbp-2 - means "serial bus protocol". This implements masstorage. Note that DV camera is NOT a masstorage.
Note that "Can't support" doesn't mean that i say "impossible and that's final". I need either a hardware or a co-developer who is able to perform testing. The stack of course will be modular, all protocols will be implemented as libraries sitting on top of raw1394 interface. The project is open.

2 All: Yesterday i've started to compile low-level OHCI card driver (ohci1394). It will be represented as standard AmigaOS device driver with the same requests set as Linux driver. Linux code is totally thread-safe so it's relatively easy to port it. It's extremely good that OpenPCI API is a 100% copy of Linux one, this helps a lot.

For more information see linux1394.org

[ Edited by Sonic on 2006/8/21 12:27 ]

Sonic

Sounds good. Good luck.

@Tronman

Uh.. Firewire works OOTB with Linux no problem. Even on peg1.

magnetic

@hooligan

Did that happen sending stuff to Moscow? I would expect that the main Russian city has better post service thanthe rest of cities.

For the ide<->fw box maybe it would be easier to make a bank transfer or send money to Sonic using Paypal so he can buy the ide<->fw box.

Heh, if we talk about buying something, i would better buy IPod or some other universal USB/FireWire device...
You know, one of my principes is buying only thing which will be really useful. The problem with plain FW<>IDE box is that not many machines are able to use it. There are not many PCs around with firewire interface. And this means i will have just to put the device on the shelf and forget about it after the development since i almost won't be able to use it for its purpose - data exchange.
But yes, a universal USB2+Firewire box would be extremely good and useful.

@sonic

I have a unused external Firewire/USB2 case for a 3,5" HD (without the HD though). If it could be interesting for your work just send me your postal address and i'll ship it this week.

Yeah, best would be a 5"14 box with universal USB2 + Firewire to IDE device, then it even would be possible to use CD/DVD read/write devices.

BTW new ipods are no more Firewire compatible
and it's a mess to connect it using USB as there is a first partition using a special format and only then the FAT32 (if pc formatted) drive... I still can't see the content of my iPod mini....which is FW compatible.

Quote:

Does this mean that firewire is really obsolete and being superseded by USB2?

Quote:
Thanks! This is incredible since i lack some portable media for a while since i've left the only company in the world which still uses ZIP drives.
This will help me to implement masstorage and then Mac-alike "slave HDD mode". It becomes quite implementable.

Sonic: When will you know if the firewire PCI card is working?

About the masstorage support, I guess it would indeed be useful for now for some people. But it also seems that if/when USB2 support is released, the need will be lower. So I think it makes sense to focus on the other firewire parts to begin with.

Regarding firewire licensing issues, does anyone know anything more (Neko?)? It seems to me there should not be any problems as this works with linux.. and I doubt they are paying anything. So presumably the only licensing costs are paid by hardware makers. But we'd better be sure about this.

Maybe you could mark the package: "Note to thieves: contains obscure Firewire-IDE adapter hardware. You don't need this."
Preferrably in French, English and Russian.

Quote:

not in a near future though, i heard rumours saying that USB2 driver developpement was stopped. I hope we'll have a comment from its author here one day.

@Sonic
forgot to say that you can leave your postal address here, sending me a private message if you still don't have access to emails.

Great, spreading such rumours really helps enormously.

Sure, we have no idea when it will be released. And it certainly would not *harm* to have masstorage for firewire too. But seeing that there is a separate effort to bring USB2 here, which has seen a lot of effort put into it already, and which may be available before any firewire project is completed, it seems to make sense to start work on firewire from a different angle.

Maybe we should make a USB2 bounty as well, if that could help bring this driver to completion?

No
Dot not do a USB2 bounty. If you are on the MOS ML you can here
NicoPPC talking of his EHCI/OHCI stack this will be out way before a
FW stack and will give very good speeds.

magnetic

Eh, of course I intended such a bounty for Nico, anything else would be madness!

Magnetic: Firewire didn't used to work OOTB in Linux or from what I
could tell a few years ago, much of any other time either. I never
got it to work correctly and I spent LOTS of time trying. I'm glad
they got it going now though.

Also, firewire is not dead-nowadays even alot of cheap clone PC mobos
at my local computer store have firewire on board, or if not, the
cards are sub-$15 if you know where to look, about $30 if you don't.
All decent camcorders still come with it. And by 'decent' I don't
mean the current crop of DVD based things either..

Also, firewire is preferred in the audio and video worlds because it
gives guarantees of data transfer accuracy that USB does not. Firewire
times things much more precisely than USB. Both standards will be
around for a long long time.

With that said, I have several firewire devices around and would be
happy to help test with them. A JVC GR-DVL915U miniDV camcorder, a
Que-Fire firewire CD burner at 24x. I can get a variety of other
firewire enclosures used for $10 or thereabouts, and stick in big HDDs
etc. Potentially, I might also have access to some real high-end
video equipment and a firewire audio mixer (sorry, the make escapes
me, it's a friends but he's got fat broadband and would let me come
over and plug it in.) Also an iBot firewire camera. It has great
quality, actually.

Finally, WRT the USB2, isn't that a Chris Hodges thing? Or is someone
else just adding the 2.0 support to Poseidon for him? DOesn't make
sense to re-invent the wheel for something we already have which
works so well.

Do I have to sign an NDA or something?

Tronman
I think you are wrong about this. IEEE1394 support has been in Debian kernel since I had my peg1 (2.4.x) Its plug and go (raw at least) Additionally, DV cams are auto mounted (well standardized ones) and are usable as web cams or with programs like Kino.

Not only that, but mass storage devices that are FW (hds, even ipods) are auto mounted and usable. so you may have had some non standard weird hardware you were trying.

USB 2 is NOT a Chris Hodges thing. Its NicoPPC and yes it uses Poseidon.

magnetic

Quote:

Heh, i've already send it to Falcon in a private message, but well, in order to avoid repeating i do it here. I hope asian terrorists will not grab it from here and send me a bomb or a virus...

142100, Russia, Podolsk, Sverdlova street, house 1, flat 83, Pavel Fedin.

[ Edited by Sonic on 2006/8/22 8:53 ]

The thing have started to build. Now i am implementing lowlevel Linux kernel functions (memory management, spinlocks, PCI access, etc) in a MorphOS userland.
Progress: ~5%.

Sonic
Gogogog... is anyone going to write up the bounty properly?

magnetic

I will.. but probably not until the weekend, I'm on the road atm.

> USB 2 is NOT a Chris Hodges thing. Its NicoPPC and yes it uses Poseidon.

Just to clarify this a bit: Poseidon added support for some USB 2.0 specific stuff in V3.x. The only thing needed for USB2.0 are lowlevel drivers which already exist for ages as Guido's ArakAttack and the yet unreleased NicoPPC drivers. The Elbox Spider driver also has limited support for USB 2.0 (but does not for example support using of USB 1.1 devices behind USB 2.0 hubs).

The NicoPPC USB drivers are /not/ an USB stack itself, but "merely"* the necessary low level drivers for talking to the host controller.

* Still a good portion of work!

thanks for clarification platon42, a lot of folks get mixed up about it.

glad to hear that NicoPPC is still working on his USB drivers, and sorry for spreading stupid rumours.

@Sonic

ok the external case will leave France by friday ! hope it reaches Mother Russia safely!

Platon

Thanks for the clarification. There should be some exciting news coming up for the mos community. And remember if you guys havent supported Poseidon please register it - these guys work hard

magnetic

Also can somebody get up the bounty requirements I think Acill can post the bounty even though Targhan isnt around.

Okay, so long, the thing builds... This means i've succesfully isolated the driver from the rest of the stuff and have written stubs for all routines which i need to implement. Currently they only panic with message "xxx is not implemented", however today i'll start getting it working. Today the driver is goind to load up, initialize itself and probe for the PCI card.
As i can see almost nobody visits MDC forums, so *please* read this topic and give me the answer. Probably you can tell NicoPPC to do it, he definitely can answer all these questions. This is one of key points.

Quote:

Beyound the lowlevel driver, did you start to port/write the stack itself and devices classes ? You can have a look to Apple MacOS X code which is freely available.

Regards
Nicolas