All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Asemann <peter.asemann@web.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] .../board/fads/flash.c confuses me - give me a hint
Date: Wed, 12 Jan 2005 18:21:45 +0100	[thread overview]
Message-ID: <41E55CA9.6080108@web.de> (raw)
In-Reply-To: <20050112165449.981DDC108D@atlas.denx.de>

> There must ne some strange fascination about the FADS port. I  really
> wonder  why  everybody  is  picking  one  of the most complicated and
> poroblematic ports...

I have an idea / a strong suggestion:
Maybe it's that this port seems to "fit" so many different CPUs and 
configurations that every Newbie thinks that he/she could easily copy 
the "right" parts of the code from there; while trying to do so, Mr. or 
Mrs. Newbie get lost in the super-enhanced or just wildly grown and 
tricky FADS code.

> Pleas ehave a loot at least at some other drivers, too.

I had and will have.

> Forget what the FADS is doing. Think about what is  needed  for  your
> own hardware, and implement this.

I'll do as I lack other options. I think it's recommended to develop the 
port for "my" hardware based upon 1.1.2? I started when 1.1.1 was the 
latest version.

Thanks a lot and best regards,

Peter Asemann

  reply	other threads:[~2005-01-12 17:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-12 14:43 [U-Boot-Users] .../board/fads/flash.c confuses me - give me a hint Peter Asemann
2005-01-12 16:54 ` Wolfgang Denk
2005-01-12 17:21   ` Peter Asemann [this message]
2005-01-12 18:47     ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2005-01-12 18:16 Nghiem, Tien
2005-01-12 19:34 ` Peter Asemann
2005-01-12 21:03   ` Tolunay Orkun
2005-01-12 22:29     ` Wolfgang Denk
2005-01-13  3:19       ` Tolunay Orkun
2005-01-12 21:06   ` Jon Loeliger
2005-01-12 22:19   ` Wolfgang Denk
2005-01-12 21:08 Nghiem, Tien
2005-01-13  8:24 Peter Pearse

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=41E55CA9.6080108@web.de \
    --to=peter.asemann@web.de \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.