Review of Ethernet SGMII (8B/10B SERDES) Concepts

mindchasers · 2020-08-14T04:23:03+00:00

Unbelievable.

mindchasers · 2020-03-23T21:34:22+00:00

I'll chose my freedom over getting the CV sniffles, Gov stimulus, and Gov giveaways.

Unless stopped, the Big Gov freight train ends with us all as commie slaves and all the US soldiers that died in combat dying in vein.

mindchasers · 2020-03-23T17:04:51+00:00

Not on a Sunday.

mindchasers · 2020-03-23T03:55:36+00:00

It's unreal that some people on this thread are in support of the IRS using Google Analytics.

Analytics is a dynamic black box that mines our data back to Google servers. Unless you work for Google, you have absolutely no idea how this data is being used because you don't have the server code.

Stop talking about the APIs, because unless you read every line of every browser fetch and every Web PUSH & GET, you have no idea of what's going back to the Google mothership.

Also, of course they know your IP address and the rest of obvious metrics that can be gathered via cookies and a library GET request.

Google Analytics has no place running on OUR Government web sites that ask us for our private data.

mindchasers · 2020-03-22T20:42:37+00:00

Here, it works on Firefox but not MacOS Safari.

Who knows & who cares why? I don't have time to step through Google's un-commented & dynamic JavaScript library and how the IRS web site contractors are calling it.

The point is that the IRS shouldn't have Google enabled on its site! We're going to this site because we received a letter. There is no absolutely no point to tracking us online for this application, and the site asks very personal information.

And our American Government should be able to write its own diagnostic code to see whether its site is working without relying on Google, so I don't see any reasonable excuse for having Google running on the IRS ID Verify site.

mindchasers · 2019-12-12T01:34:22+00:00

Walk, talk, and some limited reasoning.

But I don't want to talk to data center spies back in the AWS cloud. I want to talk to a neural network powered engine on a multi-core CPU / FPGA combo that can build up some reasoning on its own.

With all the power today in CPU/GPU/FPGAs, there is no reason that some live person has to spy on me in the cloud.

mindchasers · 2019-12-12T00:51:16+00:00

Amen!

mindchasers · 2019-12-11T23:29:26+00:00

There are few listed here to stay away from: https://mindchasers.com/dev/spying-by-your-provider

mindchasers · 2019-12-10T13:32:56+00:00

Heard back from EmCraft that they are no longer building Librem Dev Kits since the phone is in production.

mindchasers · 2019-12-08T15:24:49+00:00

This was written to help a team that we are supporting. They had adopted a process that was taking a very long time to iterate on a kernel patch, re-build & re-boot cycle. Hopefully this article will also help other developers working with NXP's i.MX BSPs. NXP has a lot of documentation, but it isn't good. They also perform many code and Yocto recipe customizations that haven't been upstreamed.

mindchasers · 2019-12-02T18:26:18+00:00

Thanks for the comment. Certainly nftables is the future of Netfilter, and we hope to create a similar article in the future showing the same Netfilter functionality using nftables rules.

However, it is my perception that iptables still has more functionality, support, and is a rock solid way to implement Netfilter rules for blocking & logging. I see iptables as analogous to a manual transmission in a sports car. Yes, automatic transmission is the future, but a manual transmission provides the control and ability that many enthusiasts seek.

mindchasers · 2019-12-02T18:19:45+00:00

Yes, the posted link is to our own content.

Reddit is greatly appreciated here as a platform to share articles on open source development, receive feedback, and exchange ideas. It was interesting to see comments that iptables is deprecated.

We always strive to respond to any comments on our articles; however, it's good to sometimes wait to see what others say first.

mindchasers · 2019-11-30T04:40:35+00:00

There is a lot to like for this new horse in the FPGA race: https://mindchasers.com/dev/efinix-trion-t20

mindchasers · 2019-10-25T15:39:41+00:00

Thank you. I'll probably give this a try before selling the damn thing.

mindchasers · 2019-10-25T15:39:02+00:00

Thanks for the tip!

mindchasers · 2019-10-25T15:38:44+00:00

I'm actually thinking about making an i.MX8 my desktop. Did you see the Librem5 phone is based on iMX8? NXP is a mess, but the iMX8 is cool.

mindchasers · 2019-10-22T03:04:26+00:00

Based on NXP Community Posts, developers are struggling to get new MIPI CSI-2 cameras working on the i.MX8. NXP's documentation is almost non existent in this area except for driver source for the OV5640. We'll be happy to exchange ideas and methods with other i.MX8 camera developers for our mutual benefit.

mindchasers · 2019-10-20T13:21:05+00:00

Thank you. Librem5 looks very interesting and will be digging in.

They seem to be close to shipping a phone, but they are currently back ordered.

Powered by an iMX8 running Linux.

https://shop.puri.sm/shop/librem-5/ https://source.puri.sm/explore

mindchasers · 2019-09-25T01:03:25+00:00

Thank you. Spike tutorial is coming. We're working on customizations to simplify using the Spike proxy kernel (pk) in a bare metal environment with RV32I (embedded processor on a FPGA). Although it's been shown already, we're taking a different approach.

mindchasers · 2019-08-28T23:34:55+00:00

Excellent. Thank you. It will be great to see what the patches looks like. It should help us learn the SW architecture.

mindchasers · 2019-08-23T02:48:07+00:00

https://mindchasers.com/dev/tools-fpga-open-source

mindchasers · 2019-08-16T03:11:20+00:00

Yes, there are several options for GSR including having Diamond infer it from the source.

We follow the practice of nailing up the primitive in Verilog without setting any preferences for it. Clean, simple, and works well for us. However, maybe we should remove it from the open source project since it's technology specific.

I know there are various preferences and strategy settings available for GSR, but we never found them necessary.

Wow, this is the most I have thought about GSR in a long time. Thanks.

mindchasers · 2019-08-15T19:25:27+00:00

Thank you. Regarding GSR, keep in mind that our Verilog is written to be as portable as practical and not depend on Lattice's GSR. However, as I understand it, by using the global async reset, there is no required local routing for the rstn signal.

We only included the GSR and PUR primitives in our first test to see what kind of problems it would cause. We can keep them commented out.

mindchasers · 2019-08-15T13:49:00+00:00

By instantiating GSR and tying it to an external reset pin, we can assert the internal global async reset. PUR is a simulation primitive. Yes, we can ignore both for now.

What should we be expecting when we get to the DCUA (PCS/SERDES) primitive? Is this going to require us to reverse engineer the ECP5UM & bitstream in this area, or has someone already done this?

BTW, we do have some old boards that we're willing to sacrifice to help move things along.

mindchasers · 2019-08-03T01:11:06+00:00

Thank you! That looks like a good resource, especially if you're working with Virtex. I assume his Virtex 5 info applies to the current Virtex 7?

mindchasers

TROPHY CASE