From: "Horvath Gyorgy" <HORVAATH@tmit.bme.hu>
To: Stewart Smith <stewart@linux.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [ANNOUNCE] New hardware - SGA155D dual STM-1/OC3 PCI ad
Date: Fri, 12 Sep 2003 10:59:40 +0200 [thread overview]
Message-ID: <200309120900.h8C908Xh011926@alpha.ttt.bme.hu> (raw)
Hi,
> ====> From Stewart Smith
> On Wed, 2003-09-10 at 00:55, Alan Cox wrote:
> > > 4. Optionally - and if I have enough time - I'd like
> > > to develop a twin-linear filesystem driver for
> > > time-stamped capture/playback for multiple channels
> > > of data - like a multi-band magnetic tape.
> > > BTW do you know an existing one?
> >
> > I've seen people do this in user space (just interleaving the disk in
> > big chunks in the app and driving it with O_DIRECT raw access) but not
> > in kernel file system space.
>
> (from memory) I think that ext2/ext3 does (or at least did) this - they
> lacked any smart logic for rapid allocations - at least for inodes in
> the same cylinder group. I think this was mentioned in the "Journaling
> the ext2 filesystem" paper.
Unfortunatelly, I have to deal with the file-system from
the FPGA as well - as from the Linux.
Probably I have not enough room to implement ext2/ext3
in the FPGA.
Anyway - I will see what...
Actually - I have my driver-skeleton up, and I can now load
firmware into the card.
That's a movement ... but lot more to do.
Sep 11 14:53:01 westel9 kernel: SGA155D[x] is a dual STM-1/OC3
Telecom. PCI adapter 0.01
Sep 11 14:53:01 westel9 kernel: SGA155D[0]: AMCC is at F3800000
Sep 11 14:53:01 westel9 kernel: SGA155D[0]: CPLD is at F3000000
Sep 11 14:53:01 westel9 kernel: SGA155D[0]: FPGA is at F2800000
Sep 11 14:53:01 westel9 kernel: PCI: Found IRQ 9 for device 02:0b.0
Sep 11 14:53:01 westel9 kernel: PCI: Sharing IRQ 9 with 00:1f.4
Sep 11 14:53:01 westel9 kernel: SGA155D[0]: AMCC mapped to f0818000
Sep 11 14:53:01 westel9 kernel: SGA155D[0]: AMCC S5933 Reset, MCSR=
00000026
Sep 11 14:53:01 westel9 kernel: SGA155D[0]: AMCC MCSR Initialization
failed
Sep 11 14:53:01 westel9 kernel: SGA155D[0]: AMCC S5933 Cold,
INTCSR=00000000
Sep 11 14:53:01 westel9 kernel: SGA155D[0]: CPLD mapped to f081a000
Sep 11 14:53:01 westel9 kernel: SGA155D[0]: CPLD Test, CPLD_TEST =
AA55
Sep 11 14:53:01 westel9 kernel: SGA155D[0]: CPLD Test, CPLD_TEST =
3CF0
Sep 11 14:53:01 westel9 kernel: SGA155D[0]: Firmware loaded,
running...
Sep 11 14:53:01 westel9 kernel: SGA155D[0]: FPGA mapped to f081c000
Sep 11 14:53:01 westel9 kernel: SGA155D[0]: FPGA Firmware ID is
D155FF02
Sep 11 14:53:01 westel9 kernel: SGA155D[0]: FPGA TEST = AA553CF0
I don't know why AMCC said that stupid 0x26 instead of 0xE6...
Others seemed OK - and the LED's blinking :-)
Best regards,
Gyuri
Gyorgy Horvath, Technical University of Budapest
-------------- Dept. of Telecom. and Telematics
Tel.: +36-1-463-1865, Fax.: +36-1-463-1865
Mail: horvaath@bme-tel.ttt.bme.hu
FTP: ttt-pub.ttt.bme.hu ./income
next reply other threads:[~2003-09-12 9:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 8:59 Horvath Gyorgy [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-10 8:38 Horvath Gyorgy
2003-09-09 14:27 Horvath Gyorgy
2003-09-09 14:55 ` Alan Cox
2003-09-10 14:05 ` Stewart Smith
2003-09-09 19:15 ` Francois Romieu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200309120900.h8C908Xh011926@alpha.ttt.bme.hu \
--to=horvaath@tmit.bme.hu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=stewart@linux.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®