From: Gene Heskett <gene.heskett@verizon.net>
To: linux-kernel@vger.kernel.org
Subject: floppy.c problems?
Date: Wed, 10 Dec 2003 17:58:41 -0500 [thread overview]
Message-ID: <200312101758.41498.gene.heskett@verizon.net> (raw)
Greetings all; Slightly offtopic but maybe I can find some info here.
I have a requirement to format and use a floppy, either mechanical
size, 256 byte sector, 18 sectors per track at 250kilobaud data rate.
I have been assured that the "superio' chip on my mobo can indeed do
that format. Soooo...
I've added 4 more lines to the floppy definition array in floppy.c,
and increased the array count at the top to match, but I don't seem
to be able to get any output, its working as usual. Stuck in 512
bytes per sector modes, 9 to the track that is.
I even turned on several debugging options, but haven't found out
where the logging is going if its working. Looks like if its doing
any debugging outputs, they're being sent to /dev/null.
Ideas?
Secondary problem too, I have a zombie of minicom that I can't kill.
Its sleeping for disk access or some such twaddle. It always trashes
the X window cli screen I run it in, and often locks up like a piece
of MS software from 1983. Surely that thing has been cleaned up and
'sane'itized for use with x somewhere along the line. Or am I useing
the wrong comm terminal utility in the first place?
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
next reply other threads:[~2003-12-10 22:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-10 22:58 Gene Heskett [this message]
2003-12-11 5:36 ` dan carpenter
2003-12-11 14:28 ` Gene Heskett
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=200312101758.41498.gene.heskett@verizon.net \
--to=gene.heskett@verizon.net \
--cc=linux-kernel@vger.kernel.org \
/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®