From: Wolfgang Denk <wd@denx.de>
To: Jeremy Bowen <Jeremy.Bowen@opennw.com>
Cc: "'Linux PPC'" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Problems with MMU: address translation for 0xXXXXXXXX failed
Date: Thu, 15 May 2003 02:23:22 +0200 [thread overview]
Message-ID: <20030515002327.EE9DAC6092@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 15 May 2003 12:05:00 +1200." <DEA23DB61B62D4118B5900508B323B84012CC7D8@OPENMAIL>
In message <DEA23DB61B62D4118B5900508B323B84012CC7D8@OPENMAIL> you wrote:
>
> I'm happy to pay a hardware maintenenace contract for if the hardware breaks
> down but if the product I bought initially contains a defect in manufacture
> then I see no reason to have to pay for this fault. The defect in this case
> is buggy firmware.
You may be wrong again.
Are you absolutely sure that it's a bug in the firmware? Please
consider the possibility that the firware was designed for a version
of the Linux kernel which showed a different behaviour. You might
want to check when the PTBASE support first appeared in the Linux
kernel and relate this to BDI2000 firmware releases.
> > You stated that you received the software "from a friend". This is
> > not exactly the same as receiving an official update from your
> > distributor.
>
> Not it is not the same, however both statements can be true with no
> contradiction.
Let's put it straight: either you (or your company) payed for an
extension of your software support, or your copy of the bdiGDB
software version 1.12 is illegal. Period.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
A bore is someone who persists in holding his own views after we have
enlightened him with ours.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2003-05-15 0:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DEA23DB61B62D4118B5900508B323B84012CC7D8@OPENMAIL>
2003-05-15 0:23 ` Wolfgang Denk [this message]
2003-05-15 3:43 Problems with MMU: address translation for 0xXXXXXXXX failed Jeremy Bowen
2003-05-15 6:34 ` Dan Malek
[not found] <DEA23DB61B62D4118B5900508B323B84012CC7D7@OPENMAIL>
2003-05-15 0:19 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2003-05-14 23:33 Jeremy Bowen
2003-05-14 23:45 ` Wolfgang Denk
2003-05-14 23:52 ` Wolfgang Denk
2003-05-14 21:15 Jeremy Bowen
2003-05-14 21:46 ` Wolfgang Denk
2003-05-13 4:19 Jeremy Bowen
2003-05-13 5:07 ` Dan Malek
2003-05-13 8:08 ` Wolfgang Denk
2003-05-13 7:55 ` Wolfgang Denk
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=20030515002327.EE9DAC6092@atlas.denx.de \
--to=wd@denx.de \
--cc=Jeremy.Bowen@opennw.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).