<set_>
It was to say, "Not easy on the senses." Lots of foul language and wondering why things look so nice online instead of my current reactions to the build process.
<set_>
Ideas.
<set_>
ServoCape, here I come.
Guest95 has joined #beagle
<Guest95>
Ciao
Guest95 has quit [Client Quit]
xet7 has joined #beagle
vigneshr has quit [Quit: Connection closed for inactivity]
Shadyman has quit [Quit: Leaving.]
vigneshr has joined #beagle
argonautx has joined #beagle
otisolsen70 has quit [Quit: Leaving]
ikarso has joined #beagle
akaWolf has quit [Ping timeout: 260 seconds]
brook has quit [Remote host closed the connection]
brook has joined #beagle
akaWolf has joined #beagle
brook has quit [Ping timeout: 252 seconds]
brook has joined #beagle
GenTooMan has quit [Ping timeout: 244 seconds]
GenTooMan has joined #beagle
brook has quit [Remote host closed the connection]
brook has joined #beagle
demirok has quit [Ping timeout: 255 seconds]
demirok has joined #beagle
demirok has quit [Ping timeout: 260 seconds]
brook has quit [Read error: Connection reset by peer]
vagrantc has joined #beagle
florian has quit [Quit: Ex-Chat]
GenTooMan has quit [Ping timeout: 255 seconds]
GenTooMan has joined #beagle
brook has joined #beagle
demirok has joined #beagle
akaWolf has quit [Ping timeout: 260 seconds]
<set_>
Thu. is the day of all days!
<set_>
If you do not chat, I will never learn things...
<set_>
I can read all day but there are things people do not confess wholely.
akaWolf has joined #beagle
<set_>
Okay...
<set_>
Are people, you-me-anyone, trying to advance in the .dtb for the BBAI-64 or are people trying to "lie low" on builds?
<set_>
I ask b/c of these ideas I have swirling. For instance, there are many parts to the BBAI-64, each will need specific tending, and then all the .dtsi, .dts, and finally a .dtb working is needed or not? See, I really do not know what peoples' thoughts are on this effort.
<set_>
And...what is the deal w/ the roboticsCape.dts?
<set_>
14 files, right!
Shadyman has joined #beagle
<set_>
In 5.10.x, there are 14 files that are associated w/ the k3-j721e and am65xx.
<set_>
I mean, does one person have one file and relay findings on what he/she finds or is it a grab bag of ideas? Or! Is everything already done and I am just barking here?
<rcn-ee>
set_: things are done to 'just' do them. things are done as users 'need' stuff..
<rcn-ee>
'are not'...
<set_>
Oh.
<set_>
Okay.
<set_>
Um, I am just a user learning. I do not know stuff yet. I know that sounds silly since I have been learning things all along.
<set_>
But...
<set_>
I was wondering: assigned-clocks = <&k3_clks 296 3>; comes from what part of k3?
outrageous has quit [Remote host closed the connection]
<set_>
It has a parent of &dphy2 but I have not come across it yet.
<set_>
I am in the 7inch-panel.dts file for the RPi.
<set_>
It is at the end of the file.
<set_>
Should I look in a file for dphy2 and then scroll around?
<set_>
Oh. Okay. I am going to download that thing and try new stuff then. Thank you, again.
argonautx has quit [Quit: Leaving]
<set_>
So, say I am building a macro enabled .dts file, would k3.h and the other files in linux-5.10.115/arch/arm64/boot/dts/ti be handy to understand?
<set_>
or...are there better files to search for directives?
<rcn-ee>
set_: the bbai64 is part of the k3-j721e* family
<set_>
Right.
<set_>
So, just search for everything k3-*?
<rcn-ee>
set_: no... see previous...
<set_>
So, nothing w/ k3-am65?
<rcn-ee>
set_: no... k3 has a few sub-archs... see my previous.. nothing more...
<zmatt>
k3 (keystone3) is just the name for a large family of SoCs
<zmatt>
or, well, a family of SoCs, dunno if it's large
<set_>
Okay.
<set_>
They have a couple.
<rcn-ee>
set_: k3 is complex... there are a few k3-j721e based kits..
<set_>
Okay, rcn-ee about the blobs. I will look to the DeviceTrees in k3-j731e-main.dtsi.
<set_>
Oh. I understand. I have seen their kits from ti.
<set_>
They have all sorts of info. too.
<rcn-ee>
set_: open TI's datasheet... *main* matches the main section, *mcu-wakeup* is the mcu section, very seperate areas on the k3..
<set_>
Okay.
<rcn-ee>
set_: the k3 is complex, ti split the *.dts's up into discrete sections..
<set_>
Oh. So it seems.
<set_>
I see their .dtsi and .dts files so far in the kernel but loosing. I am taking notes slowly. Who knows? Thank you...
<set_>
but I am losing. So many different whitepapers, source, and basic terminology to understand.
<rcn-ee>
set_: starting with the k3 would be a mistake... start with something simpler, like am335x...
<set_>
Okay.
<set_>
Thank you for your time and I will try to understand the am335x a bit more as time persists.
Archana has joined #beagle
set_ has quit [Ping timeout: 252 seconds]
ryan50 has joined #beagle
<ryan50>
Can anyone tell me if the beaglebone ai has been discontinued?
<rcn-ee>
ryan50: part shortage still going on..
<ryan50>
I see; I would like to use it for product development. Would it be reasonable to assume it will continue to be supported in the future?
<rcn-ee>
the am57xx on the bbai runs a little hot, do you need something speicifc in the am57xx?
<ryan50>
I am looking for a node that is capable of acquiring and processing real-time data with sample rates approaching 2*4Msps.
<ryan50>
At the same time it needs to be able to stream the processed data in real time.
ryan50 has quit [Ping timeout: 252 seconds]
<zmatt>
depending on the actual details that sounds like a bbb could do the job
<zmatt>
oh he left
<Archana>
I am here!
Archana has quit [Remote host closed the connection]
set_ has joined #beagle
demirok has quit [Ping timeout: 260 seconds]
CygniX has quit [Excess Flood]
CygniX has joined #beagle
ikarso has quit [Quit: Connection closed for inactivity]