public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Jared Hulbert <jaredeh@gmail.com>
To: James Hughes <JHughes@linx.co.uk>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: Trying to get MTD to do anything...
Date: Thu, 12 Jan 2006 11:14:17 -0800	[thread overview]
Message-ID: <6934efce0601121114v63ffb32brd20ced641161c3cf@mail.gmail.com> (raw)
In-Reply-To: <DB1B6B12D0E2F0469EB35A9586066B6ECE79AD@stivesemail.stives.linx.gbr>

> In fact, all I know is the register function in the driver is being called -
> i.e. the function in
>
>         module_init(init_sandgate2)
>
> the init_sandgate2 function IS being called.
>
> This function simply does the following :
>
>         return driver_register(&sandgate2_flash_driver);
>
> and a printk in the function does display.
>
> I am not sure what there is to fix. The driver gets registered, but probe is
> never called. Its correctly added to the driver structure (in fact a direct
> copy from the mainstone variant, but with name changes to match sandgate2) -
> what else is there to debug?

This is very different than what I am expecting...
Actually there is no mainstone map in 2.6.10 look at the lubbock one
for reference.
http://sosdg.org/~coywolf/lxr/source/drivers/mtd/maps/lubbock-flash.c?v=2.6.10

If the map isn't doing the probe, then maybe it expects physmap stuff?
 I've always used the platform specfic map file, so I'm not going to
be any help with the physmap.  Also I don't think the phymap stuff is
optimized yet.

       reply	other threads:[~2006-01-12 19:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DB1B6B12D0E2F0469EB35A9586066B6ECE79AD@stivesemail.stives.linx.gbr>
2006-01-12 19:14 ` Jared Hulbert [this message]
2006-01-12 21:04   ` Trying to get MTD to do anything Todd Poynor
     [not found] <DB1B6B12D0E2F0469EB35A9586066B6ECE79A1@stivesemail.stives.linx.gbr>
2006-01-12 17:11 ` Jared Hulbert
2006-01-06 11:09 James Hughes
2006-01-10 18:47 ` Jared Hulbert

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=6934efce0601121114v63ffb32brd20ced641161c3cf@mail.gmail.com \
    --to=jaredeh@gmail.com \
    --cc=JHughes@linx.co.uk \
    --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