Hello Andrew # On the other hand, the reason that I have the #BBAI is to play with some DSP on the C66x cores,
Why not use JTAG + code composer right to the DSP You obviously wouldn't have the Unix to DSP part for a product but you could play with DSP and sort out rest later Sent from Yahoo Mail on Android On Mon, Apr 13, 2020 at 5:00 PM, Andrew Reilly<[email protected]> wrote: FreeBSD isn't what runs on the Apple Mac as such. The Mac kernel, "Darwin", is derived from the CMU Mach microkernel research, with a BSD-derived kernel running as a single-server, rather than a multi-server configuration (like minix or QNX). In the CMU days, before NeXT, that was based on the original 4.2BSD distribution, but I believe that it's been spruced up a bit in the macOS days with (at least) FreeBSD's virtual memory subsystem and network stack, and a chunk of NetBSD-derived other pieces. The device drivers still live outside BSD, in Mach "DriverKit" land, which is why they're C++. The user-land is mostly FreeBSD, and has had several refreshes over the years. FreeBSD itself doesn't have a microkernel: it's old-school unikernel all the way down to the hardware, and the device drivers live in /usr/src/sys/modules or there-abouts. Sure, there almost certainly aren't as many useful-for beaglebone drivers in there. The OS was x86 and x86_64 only for a significant chunk of its life. People who wanted BSD-on-toaster were shown where to find NetBSD. I'm not entirely sure why that's changed, but my guess is that people wanted "big iron" OS to run on their big-iron Sparc, Power and now Arm systems. Why would you want to do that? I can only speak for myself, but it's more a case of not ever changing what wasn't broken: I've been running BSD since about 1986 or so. If you say that it's possible to get FreeBSD to boot on my beaglebone-AI, then I might just give it a go! On the other hand, the reason that I have the BBAI is to play with some DSP on the C66x cores, and the interface drivers seem kernel-version fragile, and all of the TI tools are clearly set up for Linux, so perhaps I'll just sit tight for now. I'm still trying to come to terms with a system that doesn't install the source and headers by default, which doesn't do "netstat" properly, which has all of these system-* commands, and which seems to bork it's USB-audio stack when left open but unused for long periods. Tracking down slow ephemerons or heisenbugs is about the least fun part of programming, IMO. I'm currently trying to wrap my head around the OpenCL-ness of the DSP access. I was expecting something in DSPBios with a mailbox system to the host, and perhaps that's there under the covers, but all of the examples use openCL, and if it aint broke, etc. Still, I'm not sure how you do "initialization" and frame-to-frame persistent state in OpenCL land. If anyone has pointers, I'd appreciate it. Cheers, Andrew ReillyM: [email protected] On 14 Apr 2020, at 03:00 , Richard Day <[email protected]> wrote: I had another look at BSD. Yes, lord only knows how you would convince the beagle to boot and root into that. Is this the thing the basis of what now runs on Apple Mac's? What would you use that for? I would miss the Linux/drivers folder too much. Are you stuck indoors as well? I will be here until June. I might as well learn BSD as well. Cheers Richard On Sun, Apr 12, 2020 at 12:31 AM Stuart Longland <[email protected]> wrote: On 10/4/20 11:46 am, Richard Day wrote: > You should have a ROOTFS and a BOOTFS. > > One is about BOOT is 20Mb and the ROOT is about 500Mb or bigger. > > The BOOT is a FAT and the ROOT is a EXT4 partition. FreeBSD doesn't use EXT4, so it may have a very different boot layout. I expect there may be EXT4 or FAT partition there for the boot-loader (uboot) but FreeBSD has its own filesystem (and its own disklabel format within its partitions). -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/d69d9d85-8861-ed7e-3b92-0a93bd428985%40longlandclan.id.au. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CABi%3DvYB%2Bd5B8GBifRM7NyeO%2BYJ8m%2BRfrY8DGLJq58dxP0S%2Bw7A%40mail.gmail.com. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/C472A98D-24A2-4E28-A4EA-FD7BFB6B9995%40bigpond.net.au. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/1253371916.168058.1586873049036%40mail.yahoo.com.
