From: Wolfram Sang <w.sang@pengutronix.de>
To: Anton Vorontsov <cbouatmailru@gmail.com>
Cc: linuxppc-dev@ozlabs.org, devicetree-discuss@ozlabs.org
Subject: Re: [PATCH 2/2] powerpc: pcm030/032: add pagesize to dts
Date: Tue, 16 Nov 2010 22:45:37 +0100 [thread overview]
Message-ID: <20101116214537.GD19893@pengutronix.de> (raw)
In-Reply-To: <20101115221156.GA25167@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 613 bytes --]
> Even worse, I seem to recall that I had once seen a manufacturer increasing the
> page-size from one charge to the next without changing the part-number, so I
> got this feeling "you can't map pagesize to manufacturer/type" which I still
> have. Sadly, this was long ago, so I can't proof it right now. Will try to dig
> up some datasheets when in the office tomorrow.
Had a look, couldn't find anything :( And now?
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <w.sang@pengutronix.de>
To: Anton Vorontsov <cbouatmailru@gmail.com>
Cc: linuxppc-dev@ozlabs.org, devicetree-discuss@ozlabs.org
Subject: Re: [PATCH 2/2] powerpc: pcm030/032: add pagesize to dts
Date: Tue, 16 Nov 2010 22:45:37 +0100 [thread overview]
Message-ID: <20101116214537.GD19893@pengutronix.de> (raw)
In-Reply-To: <20101115221156.GA25167@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 613 bytes --]
> Even worse, I seem to recall that I had once seen a manufacturer increasing the
> page-size from one charge to the next without changing the part-number, so I
> got this feeling "you can't map pagesize to manufacturer/type" which I still
> have. Sadly, this was long ago, so I can't proof it right now. Will try to dig
> up some datasheets when in the office tomorrow.
Had a look, couldn't find anything :( And now?
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 150 bytes --]
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
next prev parent reply other threads:[~2010-11-16 21:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 17:25 [PATCH 1/2] misc: at24: parse OF-data, too Wolfram Sang
2010-11-15 17:25 ` [PATCH 2/2] powerpc: pcm030/032: add pagesize to dts Wolfram Sang
2010-11-15 17:32 ` Anton Vorontsov
2010-11-15 21:06 ` Mitch Bradley
2010-11-15 21:24 ` Anton Vorontsov
2010-11-15 21:58 ` Grant Likely
2010-11-15 21:58 ` Grant Likely
2010-11-15 22:17 ` Mitch Bradley
2010-11-15 22:30 ` David Gibson
2010-11-15 22:30 ` David Gibson
2010-11-15 22:11 ` Wolfram Sang
2010-11-15 22:11 ` Wolfram Sang
2010-11-16 21:45 ` Wolfram Sang [this message]
2010-11-16 21:45 ` Wolfram Sang
2010-11-16 22:03 ` Anton Vorontsov
2010-11-15 21:41 ` [PATCH 1/2] misc: at24: parse OF-data, too Grant Likely
2010-11-15 21:41 ` Grant Likely
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=20101116214537.GD19893@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=cbouatmailru@gmail.com \
--cc=devicetree-discuss@ozlabs.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.