linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Clemens Koller <clemens.koller@anagramm.de>
To: Alex Zeffertt <ajz@cambridgebroadband.com>
Cc: linux-mtd@lists.infradead.org, linuxppc-embedded@ozlabs.org
Subject: Re: sub-module loading (was: Anyone got drivers/mtd/maps/pm828.c?)
Date: Thu, 16 Jun 2005 10:47:23 +0200	[thread overview]
Message-ID: <42B13C9B.1080403@anagramm.de> (raw)
In-Reply-To: <20050615145434.315a4b94.ajz@cambridgebroadband.com>

Hi, Alex...
good to know, that you made good progress. :-)

I just X-post this to linux-mtd so maybe somebody can have a look
at your issue, too.

I also experienced "problems" with sub-module-loading. Or maybe
I just missed something:
I need to load mtdchar and map_ram separately in order to be
able to probe my mminfo.ko module to access/mess some
SRAM in my FPGA on a MPC8540. I didn't care about that yet,
but maybe there are missing dependencies which can be solved
automagically here. Or is the sub-module loading supposed to
work like this (well, manual) as somebody might want to choose
in between i.e. mtdblock and/or mtdchar?

I'm talking about the Kernel 2.6.11.11 mtd subsystem.

Best greets,

Clemens Koller
_______________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Str. 45/1
81379 Muenchen
Germany

http://www.anagramm.de
Phone: +49-89-741518-50
Fax: +49-89-741518-19

Alex Zeffertt wrote:
> Hi Clemens,
> 
> Thanks for your help.  I've done it now (see attached).  The
> partitioning is specific to our application but it is easily modified.
> 
> I noticed a buggette in the mtd code while doing this.  If you build
> everything as a module then the sub-module loading doesn't work
> properly.  For example in gen_probe.c it says
> 
> #ifdef CONFIG_MTD_CFI_INTELEXT
> 	case 0x0001:
> 	case 0x0003:
> 		return cfi_cmdset_0001(map, primary);
> #endif
> 
> where it should really say
> 
> #if defined(CONFIG_MTD_CFI_INTELEXT) ||
>     defined(CONFIG_MTD_CFI_INTELEXT_MODULE)
> 	case 0x0001:
> 	case 0x0003:
> 		return cfi_cmdset_0001(map, primary);
> #endif
> 
> There are several problems like this.  In the end I gave up and just
> built everything except the actual mapping driver as kernel resident.
> 
> Alex
> 
> 
> On Wed, 15 Jun 2005 15:18:37 +0200
> Clemens Koller <clemens.koller@anagramm.de> wrote:
> 
> 
>>Hi, Alex!
>>
>>Hmm, I don't know the PM828 much in detail, but have you
>>tried the "generic" physmap driver which is in the kernel?
>>Just give it the base address and the size, and it should
>>probe the cfi and you are done (well, it was working fine
>>for me on my PM854).
>>Of course, you need to make sure, that your hardware / memory
>>mapping is initialized properly (which happens usually in the
>>boot loader). If it's not, let me know and I can give you
>>some code to mess around with the registers in a kernel module.
>>
>>Best greets,
>>
>>Clemens Koller
>>_______________________________
>>R&D Imaging Devices
>>Anagramm GmbH
>>Rupert-Mayer-Str. 45/1
>>81379 Muenchen
>>Germany
>>
>>http://www.anagramm.de
>>Phone: +49-89-741518-50
>>Fax: +49-89-741518-19
>>
>>
>>Alex Zeffertt wrote:
>>
>>>Hi there,
>>>
>>>I need to get flash partitions working on my PM828 development
>>>board. Has anybody already written a pm828.c?  If so I'd appreciate
>>>a look at it.
>>>
>>>TIA,
>>>
>>>Alex
>>>_______________________________________________
>>>Linuxppc-embedded mailing list
>>>Linuxppc-embedded@ozlabs.org
>>>https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>>

      reply	other threads:[~2005-06-16  8:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-14  9:47 Anyone got drivers/mtd/maps/pm828.c? Alex Zeffertt
2005-06-15 13:18 ` Clemens Koller
2005-06-15 13:54   ` Alex Zeffertt
2005-06-16  8:47     ` Clemens Koller [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=42B13C9B.1080403@anagramm.de \
    --to=clemens.koller@anagramm.de \
    --cc=ajz@cambridgebroadband.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linuxppc-embedded@ozlabs.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).