25 Jan
2005
25 Jan
'05
5:22 p.m.
I was interested in the thread about firewire audio device support
in Linux a while back. Just the other day I noticed that Presonus is
just up the road from where I live so I thought I'd drop them a line and
ask about their two firewire interfaces and if they would consider
releasing specs to the Linux audio community to get drivers written for
them. I received two responses, both of which seem promising:
Hi Jan,
We have a Linux fan within our engineering group. I feel certain that
we
could provide driver information for the development of Linux based
FireWire connectivity.
.
.
.
Please let us know who to contact.
Kind regards,
Jim Odom
President/CEO
PreSonus Corporation
225-216-7887 ext. 107
and:
Mr. Depner
I'm the engineer interested in Linux that Jim Odom spoke of. I in no
way
claim to be even an experienced Linux user, I like the idea behind
it. I
can tell you that there is ongoing development of a Linux driver for
products based on the firewire solution that we employ. The name of
the
company whose solution we use is BridgeCo...you might be able to
google some
info...no promises. I'm not sure what they've released to the open
source
community at this point...but I can tell you they are working on it.
Thanks
for your interest in PreSonus and BridgeCo, and if you find out
something...let me know!
Just thought I'd throw this out on the list to see what feedback I
get. I hope I didn't step on anyone's toes. If you know someone who
would be interested in working on drivers please pass this to them.
Contact information for Presonus is available on their web page.
Jan
25 Jan
25 Jan
6:01 p.m.
The "ongoing development of a Linux driver" for the BridgeCo hardware is
FreeBob
(http://freebob.sourceforge.net/).
Cheers,
Andreas
----- Original Message -----
From: "Jan Depner" <eviltwin69(a)cableone.net>
To: "Linux_Audio_Dev" <linux-audio-dev(a)music.columbia.edu>
Sent: Tuesday, January 25, 2005 10:58 PM
Subject: [linux-audio-dev] Firewire support in Linux
I was interested in the thread about firewire audio device support
in Linux a while back. Just the other day I noticed that Presonus is
just up the road from where I live so I thought I'd drop them a line and
ask about their two firewire interfaces and if they would consider
releasing specs to the Linux audio community to get drivers written for
them. I received two responses, both of which seem promising:
Hi Jan,
We have a Linux fan within our engineering group. I feel certain that
we
could provide driver information for the development of Linux based
FireWire connectivity.
.
.
.
Please let us know who to contact.
Kind regards,
Jim Odom
President/CEO
PreSonus Corporation
225-216-7887 ext. 107
and:
Mr. Depner
I'm the engineer interested in Linux that Jim Odom spoke of. I in no
way
claim to be even an experienced Linux user, I like the idea behind
it. I
can tell you that there is ongoing development of a Linux driver for
products based on the firewire solution that we employ. The name of
the
company whose solution we use is BridgeCo...you might be able to
google some
info...no promises. I'm not sure what they've released to the open
source
community at this point...but I can tell you they are working on it.
Thanks
for your interest in PreSonus and BridgeCo, and if you find out
something...let me know!
Just thought I'd throw this out on the list to see what feedback I
get. I hope I didn't step on anyone's toes. If you know someone who
would be interested in working on drivers please pass this to them.
Contact information for Presonus is available on their web page.
Jan 
26 Jan
26 Jan
9:09 a.m.
The "ongoing development of a Linux driver"
for the BridgeCo hardware is FreeB
ob
(http://freebob.sourceforge.net/).
i don't entirely understand how the bridgeco h/w is relevant to a
communication protocol between, say, a PreSonus audio interface and a
computer running linux. can anyone enlighten me?
--p
10:26 a.m.
Paul Davis wrote:
i don't entirely understand how the bridgeco h/w
is relevant to a
communication protocol between, say, a PreSonus audio interface and a
computer running linux. can anyone enlighten me?
"BridgeCo's Breakout Box solutions are ready-to-go reference designs for
manufacturers of music industry equipment."
See:
http://www.bridgeco.net/products/bebob/index.shtml
In other words: manufacturers can buy a complete design (including firmware
etc.) from BridgeCo and use that (and components delivered by BridgeCo and
others) to manufacture the hardware.
PreSonus is one of those "manufacturers of music industry equipment":
http://www.bridgeco.net/news/PreSonus_Media_Release.shtml
Cheers,
Andreas
10:56 a.m.
Paul Davis wrote:
but if the 1394 interface on my computer doesn't use a BridgeCo chip,
yet still recieves the data from the wire, isn't this a protocol
issue, not a h/w issue?
--p
i don't entirely understand how the bridgeco
h/w is relevant to a
communication protocol between, say, a PreSonus audio interface and a
computer running linux. can anyone enlighten me?
"BridgeCo's Breakout Box solutions are ready-to-go reference designs for
manufacturers of music industry equipment."
See:
http://www.bridgeco.net/products/bebob/index.shtml
In other words: manufacturers can buy a complete design (including firmware
etc.) from BridgeCo and use that (and components delivered by BridgeCo and
others) to manufacture the hardware.
11:47 a.m.
but if the 1394 interface on my computer doesn't
use a BridgeCo chip,
yet still recieves the data from the wire, isn't this a protocol
issue, not a h/w issue?
It *should* be but unfortunately it seems to be similar to the situation with
USB audio hardware. I do not know who can be blamed for that.
Cheers,
Andreas
1:16 p.m.
but if the 1394 interface on my computer doesn't
use a BridgeCo chip,
yet still recieves the data from the wire, isn't this a protocol
issue, not a h/w issue?
The BridgeCo Chip (the FirePod uses a DM1000) is used as a CPU core with
additinal functional blocks like a AV port (audio video port). So for example
the FirePod has some analog part and a digital part. The core of the digital
part is the DM1000 which does some signal routing etc. The communcitation
directed to the PC is done through the 1394 bus. The PHY is normaly from TI.
So far nothing special about the hardware. The interesting parts are the
protocol used for the communication. The application which is running on
those break out boxes are mostly based on the BeBoB plattform. BeBob
followes the standard protecols defined by various groups like the TA 1394 group.
So in short, yes it is only a protocol issue. You don't need a BridgeCo chip
for communication to a FirePod.
cheers,
daniel
4:38 a.m.
On Tue, Jan 25, 2005 at 03:58:39 -0600, Jan Depner wrote:
> Mr. Depner
> I'm the engineer interested in Linux that Jim Odom spoke of. I in no
> way
> claim to be even an experienced Linux user, I like the idea behind
> it. I
> can tell you that there is ongoing development of a Linux driver for
> products based on the firewire solution that we employ. The name of
> the
> company whose solution we use is BridgeCo...you might be able to
> google some
This is the chipset that the FreeBob project is working on a driver for.
> info...no promises. I'm not sure what
they've released to the open
> source
> community at this point...but I can tell you they are working on it.
> Thanks
> for your interest in PreSonus and BridgeCo, and if you find out
> something...let me know!
Good to know that there are companies out there that are willing to help
though.
- Steve
7:28 p.m.
Can you ask your contact if they can supply any information on the
PreSonus FIRESTATION? It uses Yamaha's mLAN protocol. I emailed various
addresses at Yamaha and PreSonus a while ago asking for information.
PreSonus couldn't help me, and I received only deafening silence from
Yamaha.
I'm working on a reverse-engineered mLAN driver, but it's going fairly
slowly because I keep getting sidetrackted into making other parts of
Linux 1394 suck less.
Jody
8:18 p.m.
I've forwarded the message to them and I'll let you know what I get
back.
Jan
On Wed, 2005-01-26 at 17:28, Jody McIntyre wrote:
Can you ask your contact if they can supply any
information on the
PreSonus FIRESTATION? It uses Yamaha's mLAN protocol. I emailed various
addresses at Yamaha and PreSonus a while ago asking for information.
PreSonus couldn't help me, and I received only deafening silence from
Yamaha.
I'm working on a reverse-engineered mLAN driver, but it's going fairly
slowly because I keep getting sidetrackted into making other parts of
Linux 1394 suck less.
Jody
27 Jan
27 Jan
5:40 p.m.
The word from the Presonus engineer that I've been talking to is:
Unfortunately I cannot help in this matter.
Yamaha's mLAN protocol is
a
proprietary system and we were not involved in driver development.
Therefore, we don't actually possess any information that would be
helpful
to anyone on the mailing list. I'm sure everyone on the list knows
this
already, but most 1394 audio solutions are rooted in the IEC 61883-6
and
AM824 standards. Knowing these documents back and forth would be a
great
place to start.
Jan
7032
days inactive
7034
days old
linux-audio-dev@lists.linuxaudio.org
12 comments
7 participants
participants (7)
-
Andreas Kuckartz -
Daniel Wagner -
Frank Barknecht -
Jan Depner -
Jody McIntyre -
Paul Davis -
Steve Harris