Hello, Does anybody have a kernel config or some hints for the Atmel AT91SAM9G20 ? I see work was done a few years ago on a very similar SoC here: http://bsdimp.blogspot.com/2007/03/followup-atmel-at91-family-work.html Working on getting FreeBSD running on this: http://www.glomationinc.com/product_9G20i.html Shelby
Hi,
I'm owner of a new VIA SN10000 mini-ITX mainboard which comes together
with VIA C7 processor. During boot it is detected as:
CPU: VIA Esther processor 1000MHz (997.51-MHz 686-class CPU)
Origin = "CentaurHauls" Id = 0x6a9 Stepping = 9
Features=0xa7c9baff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,APIC,SEP,MTRR,PGE,CMOV,PAT,CLFLUSH,ACPI,MMX,FXSR,SSE,SSE2,TM,PBE>
Features2=0x181<SSE3,EST,TM2>
VIA Padlock Features=0x3fcc<RNG,AES,AES-CTR,SHA1,SHA256,RSA>
As far as I understand, this processor should support 64-bit mode and
I should be able to boot amd64 FreeBSD.
Playing with memstick image for amd64 I get:
"CPU doesn't support long mode"
As far as I've checked, I'm missing AMDID_LM flag, as the expression
from bootinfo64.c:
/* Check for long mode. */
do_cpuid(0x80000001, regs);
return (regs[3] & AMDID_LM);
Returns 0, as regs[3] is 0.
As far as I've checked the mailing lists, there was an issue with
missing support for CentaurHauls vendor, but this is not the case, as
the failing check is later in the code.
Do anyone has any experience with this family of processors? Are they
different brands (supporting 64-bit mode and not)? I tried to look for
(Continue reading)
On Thursday 03 December 2009 01:35 pm, Wiktor Niesiobedzki wrote: > Hi, > > I'm owner of a new VIA SN10000 mini-ITX mainboard which comes > together with VIA C7 processor. During boot it is detected as: > CPU: VIA Esther processor 1000MHz (997.51-MHz 686-class CPU) > Origin = "CentaurHauls" Id = 0x6a9 Stepping = 9 > > Features=0xa7c9baff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,APIC,SEP,MTRR,PG >E,CMOV,PAT,CLFLUSH,ACPI,MMX,FXSR,SSE,SSE2,TM,PBE> > Features2=0x181<SSE3,EST,TM2> > VIA Padlock Features=0x3fcc<RNG,AES,AES-CTR,SHA1,SHA256,RSA> > > As far as I understand, this processor should support 64-bit mode > and I should be able to boot amd64 FreeBSD. No, C7 does not support long mode. New Nano family does. Jung-uk Kim
Hi, Where do you exactly see that this cpu supports amd64? Why do you need it on an embedded platform? Regards, Andras On Csü, December 3, 2009 7:35 pm, Wiktor Niesiobedzki wrote: > Hi, > > > I'm owner of a new VIA SN10000 mini-ITX mainboard which comes together > with VIA C7 processor. During boot it is detected as: CPU: VIA Esther > processor 1000MHz (997.51-MHz 686-class CPU) Origin = "CentaurHauls" Id = > 0x6a9 Stepping = 9 > Features=0xa7c9baff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,APIC,SEP,MTRR,PGE,CMOV, > PAT,CLFLUSH,ACPI,MMX,FXSR,SSE,SSE2,TM,PBE> > Features2=0x181<SSE3,EST,TM2> > VIA Padlock Features=0x3fcc<RNG,AES,AES-CTR,SHA1,SHA256,RSA> > > > As far as I understand, this processor should support 64-bit mode and > I should be able to boot amd64 FreeBSD. > > > Playing with memstick image for amd64 I get: > "CPU doesn't support long mode" > >(Continue reading)
2009/12/3 Jung-uk Kim <jkim@...>: >> As far as I understand, this processor should support 64-bit mode >> and I should be able to boot amd64 FreeBSD. > > No, C7 does not support long mode. New Nano family does. > Yes, that's where I got mislead. I've read about Nano processor and that's supporting 64-bit, and I had the impression that it is the same for C7. My mistake. And i thought about 64bit system, as I'm planning to use ZFS and as I understand, this 64bit architecture is recommended. Any way - thanks for clarification. Cheers, Wiktor Niesiobedzki
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o misc/136889 embedded [nanobsd] [path] nanobsd error reporting and other ref o misc/135588 embedded [nanobsd] simple patch for adding amd64 support o misc/52256 embedded [picobsd] picobsd build script does not read in user/s o kern/42728 embedded [picobsd] many problems in src/usr.sbin/ppp/* after c 4 problems total.
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o misc/136889 embedded [nanobsd] [path] nanobsd error reporting and other ref o misc/135588 embedded [nanobsd] simple patch for adding amd64 support o misc/52256 embedded [picobsd] picobsd build script does not read in user/s o kern/42728 embedded [picobsd] many problems in src/usr.sbin/ppp/* after c 4 problems total.
Hi. Has anyone set up cross-compilers / cross-debuggers on Windows (including using Cygwin) to compile applications for FreeBSD and debug them from Windows? If so, can you please send me any information, links, etc.? Please reply directly to me (also) as I’m not subscribed to the list. Much thanks, Arnold Robbins
Hi, On Dec 15, 2009, at 10:40, Arnold Robbins wrote: > Has anyone set up cross-compilers / cross-debuggers on Windows (including > using Cygwin) to compile applications for FreeBSD and debug them from > Windows? If so, can you please send me any information, links, etc.? Your best bet is probably to install FreeBSD in a virtual machine on top of your Windows installation. Regards, Brix -- -- Henrik Brix Andersen <brix@...>
Arnold Robbins wrote: > Hi. > > > > Has anyone set up cross-compilers / cross-debuggers on Windows (including > using Cygwin) to compile applications for FreeBSD and debug them from > Windows? If so, can you please send me any information, links, etc.? why the effort of making cross compiling tools ? if one need to develop application for given operating system, isn't more convenient to use the os as primary incubator for that software? + using virtualization is giving you false idea of how your app and underline os perform and interact with each other. take spare machine install needed version of freebsd using handbook and online how-to's on how to configure ssh and log in from your windows machine if you don't have the skills to manage sole freebsd machine as both desktop and develop environment. thus you have box to torture and you already have compiler, debugger et cetera...
RSS Feed3 | |
|---|---|
18 | |
19 | |
9 | |
14 | |
14 | |
41 | |
21 | |
28 | |
21 | |
26 | |
17 | |
7 | |
14 | |
6 | |
4 | |
22 | |
156 | |
78 | |
16 | |
8 | |
31 | |
6 | |
18 | |
9 | |
14 | |
8 | |
6 | |
17 | |
5 | |
21 | |
18 | |
13 | |
8 | |
8 | |
10 | |
8 | |
28 | |
44 | |
39 | |
19 | |
16 | |
19 | |
9 | |
34 | |
13 | |
17 | |
18 | |
28 | |
33 | |
9 | |
5 | |
23 | |
47 | |
19 | |
63 | |
32 | |
15 | |
8 | |
23 | |
15 | |
24 | |
44 | |
29 | |
25 | |
74 | |
27 | |
22 | |
22 | |
8 | |
11 | |
16 | |
25 | |
7 | |
9 | |
15 | |
15 | |
4 | |
4 |
