From: acrux <acrux_it@libero.it>
To: linuxppc-dev@lists.ozlabs.org
Subject: sam460ex, sm501 incorrect device id with kernel >=linux-2.6.39
Date: Sun, 27 Nov 2011 17:37:48 +0100 [thread overview]
Message-ID: <20111127173748.9f235741.acrux_it@libero.it> (raw)
Acube Sam460ex has SM502 as onboard video.
I got this with any kernel newer than 2.6.38.x thus the framebuffer is lost too:
root@sam4x0:~# diff dmesg-2.6.38.8 dmesg-2.6.39.4
1,2c1,3
< Using PowerPC 44x Platform machine description
< Linux version 2.6.38.8-Sam460ex (root@sam4x0) (gcc version 4.5.3 (CRUX PPC) ) #1 Fri Nov 11 22:07:53 CET 2011
---
> Using Canyonlands machine description
> Initializing cgroup subsys cpu
> Linux version 2.6.39.4-Sam460ex (root@sam4x0) (gcc version 4.5.3 (CRUX PPC) ) #1 Fri Nov 11 19:06:02 CET 2011
17c18
[cut]
161,179c165,167
< sm501 0001:00:06.0: SM501 At f5480000: Version 050100c0, 64 Mb, IRQ 19
< sm501 0001:00:06.0: setting M1XCLK to 144000000
< sm501 0001:00:06.0: setting MCLK to 72000000
< sm501-usb[0] [mem 0xd84040000-0xd8405ffff]
< sm501-usb[1] [mem 0xd83fc0000-0xd83ffffff]
< sm501-usb[2] [irq 19]
< serial8250.10: ttyS2 at MMIO 0xd84030000 (irq = 19) is a ST16654
< serial8250.10: ttyS3 at MMIO 0xd84030020 (irq = 19) is a ST16654
< sm501-fb[0] [mem 0xd84080000-0xd8408ffff]
< sm501-fb[1] [mem 0xd84100000-0xd8414ffff]
< sm501-fb[2] [mem 0xd80000000-0xd83fbffff]
< sm501-fb[3] [irq 19]
< sm501-fb sm501-fb.80: fb sm501fb-crt disabled at start
< Console: switching to colour frame buffer device 100x37
< sm501-fb sm501-fb.80: fb0: sm501fb-crt frame buffer
< sm501-fb sm501-fb.80: fb sm501fb-panel enabled at start
< sm501-fb sm501-fb.80: fb1: sm501fb-panel frame buffer
< of:sata-dwc 4bffd1000.sata: id 0, controller version 1.82
< of:sata-dwc 4bffd1000.sata: DMA initialized
---
> sm501 0001:00:06.0: incorrect device id c0000105
> sata-dwc 4bffd1000.sata: id 0, controller version 1.82
> sata-dwc 4bffd1000.sata: DMA initialized
181,182c169
< ata1: SATA max UDMA/133 irq 31
< Fixed MDIO Bus: probed
---
> ata1: SATA max UDMA/133 irq 34
[...]
btw, i remember that i also receive a kernel panic if MTD support is enabled with any kernel newer than 2.6.36.x
regards,
--nico
--
acrux <acrux_it@libero.it>
next reply other threads:[~2011-11-27 16:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-27 16:37 acrux [this message]
2011-11-28 12:12 ` sam460ex, sm501 incorrect device id with kernel >=linux-2.6.39 Josh Boyer
2011-11-28 19:56 ` acrux
2011-11-28 20:22 ` Anatolij Gustschin
2011-12-02 14:48 ` acrux
2011-12-02 15:35 ` Anatolij Gustschin
-- strict thread matches above, loose matches on Subject: below --
2011-11-29 1:00 acrux_it
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=20111127173748.9f235741.acrux_it@libero.it \
--to=acrux_it@libero.it \
--cc=linuxppc-dev@lists.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).