Re: [fedora-arm] trimslice build tf101?

2013-10-21 Thread Gordan Bobic
If you can find instructions for getting any version of any distro 
running on the TF101, you can run any distro on it. You just have to use 
whatever kernel somebody got working on the device with your prefered 
distro userspace. I have many machines running that way.


On 10/20/2013 06:10 PM, Brian Kosick wrote:

Please forgive me if I'm incorrect about this,  I'm a N00b with arm
devices.   It looks like the tf101 does support device tree.   Here's a
link to cyanogenmod device tree code for it

https://github.com/RaymanFX/device_asus_tf101

There are reports of getting ubuntu running on a tf101
https://wiki.ubuntu.com/Touch/Devices/tf101
http://forum.xda-developers.com/showthread.php?t=2168473

I'm willing to do legwork, can I virtualize a specific arm device?  I've
done stints as build manager at my place of employment and have setup
and maintain a koji build farm and bodhi instance at my place of
employment.   I just need to bootstrap my brain into the arm world view

It seems to me that device tree is arms answer to a bios/post. As in
here's a list of devices/chipsets I know about on this device.

On Oct 20, 2013 5:59 AM, Peter Robinson pbrobin...@gmail.com
mailto:pbrobin...@gmail.com wrote:

  Hi All,
 
  I have an aging Asus tf101 with the detachable keyboard and am
getting
  fairly tired of the android app ecosystem.   I was wondering
since the
  trimslice and the tf101 both share the tegra 2 chipset if anyone
had tried
  it on this device yet?   and if so could share their expereince?

I'm not aware of anyone who's got it working. There's a few things
we'd need to be able to support it well (this goes for pretty much any
device by any SoC manufacturer) and those are:
- Unlocked boot loader with device tree support
- In kernel device tree

Unfortunately most of the current older devices don't support device
tree which is a necessity for OOTB support on Fedora these days. Any
tegra based device that runs a kernel newer than 3.7 should have this
as all the non DT support for tegra platforms was ripped out in that
release. The tegra2 support is pretty reasonable now with basic video
support and will get better as the upstream driver code makes it to a
stable and usable driver.

Peter



___
arm mailing list
arm@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/arm



___
arm mailing list
arm@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/arm

Re: [fedora-arm] u-boot update testing

2013-10-21 Thread Nicolas Chauvet
2013/10/21 Dennis Gilmore den...@ausil.us

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Hi All,

 I have proposed
 https://admin.fedoraproject.org/updates/uboot-tools-2013.10-2.fc20 as a
 blocker for beta I would appreciate as many people testing it as
 possible and providing karma in bodhi, thanks.


Do you have a minimal image to test on Wandboard quad with this updated
u-boot?
So something closer to Beta than TC2 since TC5 isn't booting for me.
Just to share a reference
http://fedoraproject.org/wiki/User:Mrunge/Wandboard_quad

I've tested the previous build on my AC100 and it worked (despite it's
still missing keyboard support in uboot upstream).

Thx
Nicolas (kwizart)
___
arm mailing list
arm@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/arm

Re: [fedora-arm] Fwd: Does clock_gettime support CLOCK_REALTIME_ALARM and CLOCK_BOOTTIME_ALARM?

2013-10-21 Thread Dan Horák
On Tue, 15 Oct 2013 12:38:17 +0100
Peter Robinson pbrobin...@gmail.com wrote:

 Hi Dan,
 
 I suspect this is one for Jon/Kyle or others but looking through
 kernel bits and patches it seems that these features are completely
 agnostic to HW and in fact the patches [1] seem to have come from the
 ARM community from Android Alarm Timers [2]. One thing I would check
 is if on the particular platform being tested against has a RTC
 registered. We build a few RTCs into the kernel and dozens of other
 less common ones as modules.

I think https://lkml.org/lkml/2013/10/18/518 will be for Kyle, likely
we will need a backport to Fedora kernels


Dan

 Peter
 
 [1] https://lkml.org/lkml/2011/4/19/553
 [2] https://lwn.net/Articles/429925/
 
 On Tue, Oct 15, 2013 at 7:26 AM, Dan Horák d...@danny.cz wrote:
  forwarding a message from our Ruby maintainer asking for help
 
  looks like a kernel problem, please see also
  https://bugs.ruby-lang.org/issues/9008#note-3
 
 
  Dan
 
   Původní zpráva 
  Předmět:Does clock_gettime support CLOCK_REALTIME_ALARM and
  CLOCK_BOOTTIME_ALARM?
  Datum:  Thu, 10 Oct 2013 13:48:01 +0200
  Od: Vít Ondruch vondr...@redhat.com
  Komu:   arm@lists.fedoraproject.org
 
 
 
  Hi,
 
  I am trying to build Ruby 2.1 for F21 and I observe following test
  errors:
 
 3) Error:
  TestProcess#test_clock_getres_constants:
  Errno::E524: Unknown error 524 - clock_getres
   
  /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1752:in
  `clock_getres' 
  /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1752:in
  `block in
  test_clock_getres_constants' 
  /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1749:in
  `each' 
  /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1749:in
  `test_clock_getres_constants'
 4) Error:
  TestProcess#test_clock_gettime_constants:
  Errno::E524: Unknown error 524 - clock_gettime
   
  /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1676:in
  `clock_gettime' 
  /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1676:in
  `block in
  test_clock_gettime_constants' 
  /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1673:in
  `each' 
  /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1673:in
  `test_clock_gettime_constants'
 
 
  It looks like CLOCK_REALTIME_ALARM and CLOCK_BOOTTIME_ALARM are not
  supported, but the error code is completely strange to me.
  According to the documentation, it should return EINVAL.
 
  http://pubs.opengroup.org/onlinepubs/9699919799/functions/clock_getres.html
|
| [EINVAL]
| The clock_id argument does not specify a known clock.
 
  Any help is appreciated.
 
  Thanks
 
 
 
  Vít
 
 
 
 
  P.S. This is my upstream report:
  http://bugs.ruby-lang.org/issues/9008 P.S.2 I am not subscribed to
  this list, please keep me in the CC.
 
 
 
  ___
  arm mailing list
  arm@lists.fedoraproject.org
  https://admin.fedoraproject.org/mailman/listinfo/arm
___
arm mailing list
arm@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/arm