Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Pete Popov <ppopov@embeddedalley.com>
To: Ulrich Eckhardt <eckhardt@satorlaser.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Fixes to MTD flash driver on AMD Alchemy db1100 board
Date: Sat, 26 Feb 2005 14:04:03 -0800	[thread overview]
Message-ID: <4220F253.6060508@embeddedalley.com> (raw)
In-Reply-To: <200502221632.53448.eckhardt@satorlaser.com>

Ulrich Eckhardt wrote:
> Pete Popov wrote:
> 
>>Here is a 2.6 patch that gets rid of all the Au1x mapping files and
>>replaces them with a single file. 
> 
> 
> Big step forward, this looks much cleaner and easier to maintain!
> 
> Just a few nits:
> 
> 1. mymtd = do_map_probe("cfi_probe", &alchemy_map);
> 
> Doesn't this mean that the Alchemy flash driver depends on the CFI interface? 
> I also see that CONFIG_MTD_CFI is not set in the configfiles for some boards.
> 
> 2. If above do_map_probe() returns NULL, the ioremap()ed memory is leaked. 
> Doesn't matter that much probably, but is trivial to fix.
> 
>  if (!mymtd)
>  {
>   iounmap( alchemy_map.virt);
>   return -ENXIO;
>  }
> 
> 3. No need to cast the parameter to iounmap(), it should happily digest 
> whatever ioremap() returns. If that gives warnings, something different is 
> going wrong in between. ;)

Thanks, I took care of all this. I removed the multiple drivers in 
favor of the single, simplied driver. I pushed the updates in 
linux-mips head, and the mtd community tree. To use these changes 
with linux-mips 2.4 branch, you have to patch-in the entire mtd 
tree. However, even then I had some compile problems that were not 
related to the changes I made, so I don't know if you can still use 
the latest mtd tree with a 2.4 kernel.

Pete

      reply	other threads:[~2005-02-27 22:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-21  5:01 Fixes to MTD flash driver on AMD Alchemy db1100 board Josh Green
2005-02-21  5:23 ` Pete Popov
2005-02-21 10:44 ` Ulrich Eckhardt
2005-02-21 23:57   ` Josh Green
2005-02-22  6:06     ` Josh Green
2005-02-22  7:25       ` Pete Popov
2005-02-22 15:32         ` Ulrich Eckhardt
2005-02-26 22:04           ` Pete Popov [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=4220F253.6060508@embeddedalley.com \
    --to=ppopov@embeddedalley.com \
    --cc=eckhardt@satorlaser.com \
    --cc=linux-mips@linux-mips.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