But tbh I'm not sure whether I want to support this device officially
(in-tree) because the RPi doesn't support initrds which means potentially
a big change to how I build the kernels and modules packages;
In my experiments with ARMedSlack on a Seagate DockStar, I remember
using a mkboot
On Wed, 2012-06-20 at 07:45 +0100, Davide wrote:
I've no idea whether the installer works directly on that platform,
but you can get the miniroot working as long as you have a working
kernel for the hardware.
Look at the bottomb section in the supported platforms ... there is a
paragraph on
I've no idea whether the installer works directly on that platform,
but you can get the miniroot working as long as you have a working
kernel for the hardware.
Look at the bottomb section in the supported platforms ... there is a
paragraph on unofficially supported platforms. Look at them
On Thu, 2012-06-21 at 08:20 +0100, Davide wrote:
I've no idea whether the installer works directly on that platform,
but you can get the miniroot working as long as you have a working
kernel for the hardware.
Look at the bottomb section in the supported platforms ... there is
a
AC100 uses tegra chipset. I wonder how much work would it take to add the other
bits and pieces to the armedslack kegra kernel to make it usable on the AC100.
Regards
David
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
On Thu, 21 Jun 2012, Davide wrote:
AC100 uses tegra chipset. I wonder how much work would it take to add
the other bits and pieces to the armedslack kegra kernel to make it
usable on the AC100.
root@pepa:~/ac/source/k/configs# grep AC100 config-tegra
root@pepa:~/ac/source/k/configs#
I
AC100 uses tegra chipset. I wonder how much work would it take to add
the other bits and pieces to the armedslack kegra kernel to make it
usable on the AC100.
root@pepa:~/ac/source/k/configs# grep AC100 config-tegra
root@pepa:~/ac/source/k/configs#
I checked in menuconfig and couldn't see
AC100 uses tegra chipset. I wonder how much work would it take to add
the other bits and pieces to the armedslack kegra kernel to make it
usable on the AC100.
root@pepa:~/ac/source/k/configs# grep AC100 config-tegra
root@pepa:~/ac/source/k/configs#
I checked in menuconfig and couldn't see it
Looking at teh config I think this would need to be enabled fro the
AC100/dynabook AZ
# CONFIG_MACH_PAZ00 is not set
This looks like : http://cateee.net/lkddb/web-lkddb/MACH_PAZ00.html
Might also be necessary to enable some grafix hardware like:
CONFIG_FB_NVIDIA
And here are some other bits
Might also be necessary to enable some grafix hardware like:
CONFIG_FB_NVIDIA
This depends on CONFIG_PCI which isn't for Tegras.
And here are some other bits and pieces that might be necessary:
CONFIG_MMC_SDHCI_TEGRA
I've added this as a module to the initrd and the installer.
Once I push
But are you using the serial console on your tegra device or an ordinary
console ?
Yes it uses serial. The graphics support isn't in the mainline kernel yet
I don't think.
Will the kernel you've build the screen on the AC100 ?
Will the screen work, if that's what you're asking - no idea;
And here are some other bits and pieces that might be necessary:
CONFIG_MMC_SDHCI_TEGRA
This one won't build as a module and I can't compile it into the kernel as
I build the main MMC support as a module (which I'm not changing).
Hopefully the kernel will build with AC100 support though so
12 matches
Mail list logo
