linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: sgosavi1 <Sachin.Gosavi@emerson.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: Kernel panic when loading the IDE controller driver
Date: Wed, 13 Feb 2019 05:53:06 -0700 (MST)	[thread overview]
Message-ID: <1550062386389-0.post@n7.nabble.com> (raw)
In-Reply-To: <558c15bc-75d0-d02a-8a78-8155838b8809@c-s.fr>

> Why using 4.15.13 which is obsolete instead of using one of the Long 
> Term Support versions which are still maintained, like 4.14 or 4.19 ? 
> (see the complete list at https://www.kernel.org/category/releases.html)

Well, when I started this task 4.15.13 was probably the latest stable
release and hence we decided to port this version. In the older kernel, we
have the m8260_setup.c source file for our board where the function
"io_block_mapping" was used to configure the non-standard IO port address
starting at 0xe0000000 location. This address was passed as the base address
followed by control address and IRQ number to the ide-core.ko module. In the
new kernel we do not have an option to send these addresses and IRQ numbers
as arguments to the driver. Instead the ide-generic.c source file in the new
kernel uses the standard IO port values and IRQ values. I modified the code
in the above file to used the addresses and IRQ number we used in the past.
Also, added code in the "MMU_init" function call available under
arch/PowerPC/init_32.c to setup the IO port address range by adding the
"io_block_mapping" call and the required IO port address range.

Is there anything else that needs to be added or how can we configure the
desired IO address range in the new kernel?

Thanks,
Sachin



--
Sent from: http://linuxppc.10917.n7.nabble.com/linuxppc-dev-f3.html

  reply	other threads:[~2019-02-13 12:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-13 11:01 Kernel panic when loading the IDE controller driver sgosavi1
2019-02-13 11:46 ` Christophe Leroy
2019-02-13 12:24   ` sgosavi1
2019-02-13 12:31     ` Christophe Leroy
2019-02-13 12:53       ` sgosavi1 [this message]
2019-02-13 15:27         ` Christophe Leroy
2019-02-14  8:17           ` sgosavi1
2019-02-14 18:14             ` Michal Suchánek
2019-02-15 11:27               ` sgosavi1
2019-02-21  8:18                 ` sgosavi1
2019-02-14 17:54           ` Christophe Leroy
     [not found]             ` <CGME20190226115150eucas1p2f759d8df50102507a0ee66c4ab36003f@eucas1p2.samsung.com>
2019-02-26 11:51               ` Bartlomiej Zolnierkiewicz

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=1550062386389-0.post@n7.nabble.com \
    --to=sachin.gosavi@emerson.com \
    --cc=linuxppc-dev@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).