2008-09-18 11:47:12 Configure kernel for Firewire (IEEE 1394)?
Barrett Dillow (UNITED STATES)
Message: 62389
I am working on a project that is trying to use a Blackfin CM-BF537E with Firewire (IEEE 1394). I saw some traffic from a couple years ago on the uClinux mailing list that it was patched to support 1394. I downloaded the toolchain and tried configuring the kernel for uClinux-dist-2008R1.5-RC3 to include 1394 support.
I couldn't find the option using either 'make menuconfig' or 'make config'. I tried drilling down into every sub-menu I could. I grepped the .config file looking for something commented out or set to false that mentioned either 1394 or firewire, but failed. One thing I noticed in my attempts to configure it, though, was that the 'Plug and Play' submenu in menuconfig has no sub-options, despite having the "-->" to the right of it. Is firewire hiding in there and Somehing in my system is broken? I didn't see it in the bus section, either.
All of my toolchain is 2008R1.5-RC3 downloaded from this site.
Thanks in advance,
Barrett
QuoteReplyEditDelete
2008-09-18 16:09:45 Re: Configure kernel for Firewire (IEEE 1394)?
Mike Frysinger (UNITED STATES)
Message: 62402
it isnt going to show up in kernel menus unless you make it possible
read drivers/ieee1394/Kconfig and you see:
menu "IEEE 1394 (FireWire) support"
depends on PCI || BROKEN
Blackfin does not suppot PCI, so you may have a tough go of it ...
QuoteReplyEditDelete
2008-09-19 15:44:55 Re: Configure kernel for Firewire (IEEE 1394)?
Barrett Dillow (UNITED STATES)
Message: 62451
Thanks.
My hardware guy now tells me our FPGA will be doing all the firewire data arbitration for me and it'll appear as memory-mapped IO. So I won't have to figure out how to get 1394 in the kernel anyway.
QuoteReplyEditDelete
2008-09-19 15:55:47 Re: Configure kernel for Firewire (IEEE 1394)?
Mike Frysinger (UNITED STATES)
Message: 62452
that'll probably make everybody's life easier as i dont think firewire in embedded linux devices is terribly common ... which is probably why much of the code base is reliant on PCI