From: Aras Vaichas <arasv@magellan-technology.com>
To: MTD-LIST <linux-mtd@lists.infradead.org>
Subject: Re: Read/nBusy via interrupt
Date: Mon, 01 Nov 2004 11:01:59 +1100 [thread overview]
Message-ID: <41857CF7.3050402@magellan-technology.com> (raw)
In-Reply-To: <1099044978.22387.557.camel@thomas>
>
>>Thomas, your reply to my email was so ridiculously over the top and harsh.
>
> Sorry, It was not my intention to offend you.
No problem, it's good that we can all get flared up now again. It shows that we
are passionate about what we do. In the end, it is just a job and it pays the
bills. So no need to get so serious about it, there's so much more to life than
being angry geeks! ;)
jasmine@linuxgrrls.org wrote:
> Because hardware engineers usually design the hardware to be as flexible
> as possible, in light of the fact that they don't know how the operating
> system is going to want to use the hardware.
If this is the case, then the system isn't properly specified, and software
needs to talk to hardware a little more.
On last Friday, the guy responsible for our hardware had to finish routing our
PCB. We are replacing an ATmega128 (8bit) with the AT91RM9200 (32bit) in the
*same* space (plus adding SDRAM, FLASH, Dataflash, ethernet and USB!). There
came a point where he could route no more connections because there just wasn't
enough room left - plus the law-of-diminishing-returns was beginning to apply.
Therefore, he needed to know which signals were absolutely necessary for a
fully functional design (according to the system spec.) So I had tell him that
he could use the smaller MTD (without READY/nBUSY) and that it would still work
with the existing software.
jasmine@linuxgrrls.org wrote:
> So, connect the damned wire and shut up.
ROFL! So, in a word, "no", because there was no pin for the wire to be
connected to!
It looks like we have thoroughly answered Ben's original question from various
passionate points of view.
regards,
Aras
prev parent reply other threads:[~2004-11-01 0:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 23:06 Read/nBusy via interrupt Ben Dooks
2004-10-28 23:13 ` Thomas Gleixner
2004-10-28 23:43 ` Aras Vaichas
2004-10-29 7:33 ` Thomas Gleixner
2004-10-29 9:56 ` Aras Vaichas
2004-10-29 9:57 ` jasmine
2004-10-29 10:16 ` Thomas Gleixner
2004-11-01 0:01 ` Aras Vaichas [this message]
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=41857CF7.3050402@magellan-technology.com \
--to=arasv@magellan-technology.com \
--cc=linux-mtd@lists.infradead.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