From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: expose PB1176 ROM in debugfs
Date: Sat, 4 Sep 2010 04:13:10 +0200 [thread overview]
Message-ID: <201009040413.10445.marek.vasut@gmail.com> (raw)
In-Reply-To: <AANLkTik4F8VnCota=Jp+pZPg3QHvr-dKzy3cuVXJeMu7@mail.gmail.com>
Dne P? 3. z??? 2010 23:38:54 Linus Walleij napsal(a):
> Ping on this David, you have an opinion? debugfs ROM or
> MTD ROM mapping?
Hey, I'd be for having this exposed through mtd_rom too. Cheers
>
> Yours,
> Linus Walleij
>
> 2010/7/18 Linus Walleij <linus.ml.walleij@gmail.com>:
> > 2010/7/18 Russell King - ARM Linux <linux@arm.linux.org.uk>:
> >> On Wed, Jul 07, 2010 at 02:05:39PM +0200, Linus Walleij wrote:
> >>> This exposes the PB1176 ROM as a simple 16KiB file in debugfs so
> >>> that it can be copied out and disassembled with some
> >>> objcopy+objdump massage for example. I used this to find out how
> >>> the ROM handled the CharLCD.
> >>
> >> Would it be better to expose this through a mtd ROM mapping (map_rom) ?
> >
> > This is more convenient I think.
> >
> > I don't know the actual purpose of MTD ROM mappings, so
> > paging David on this.
> >
> > It has the small upside of only getting compiled in if you select
> > CONFIG_DEBUG_FS, and getting a distinct name in debugfs
> > rather than /dev/mtdN.
> >
> > Also I can now cp /debugfs/pb1176-ROM foo.bin
> > Is this possible with mtdblocks or do you have to dd if=... ?
> >
> > Yours,
> > Linus Walleij
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2010-09-04 2:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 12:05 [PATCH] ARM: expose PB1176 ROM in debugfs Linus Walleij
2010-07-18 19:47 ` Russell King - ARM Linux
2010-07-18 20:39 ` Linus Walleij
2010-09-03 21:38 ` Linus Walleij
2010-09-04 2:13 ` Marek Vasut [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=201009040413.10445.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).