Teledatics has launched a crowdfunding campaign for the TD-HALOM HaloMax Wi-Fi HaLow module available in LGA and M.2 form factors for long-range and low-power connectivity, as well as HaLow development boards based on the module and various daughterboards for expansion. The wireless module, powered by Newracom’s NRC7394 SoC, is the product of a collaboration between Newracom and Teledatics. According to Zac Freeman, VP of Marketing & Sales at Newracom, the HaloMax module is “the highest output power Wi-Fi HaLow module available on the market. The Teledatics TD-HALOM module transmits at the highest allowable FCC power output and offers a Maximum Range HaLow solution.” Earlier this year, Teledatics broke the record for the longest distance for a Wi-Fi HaLow connection using the HaloMax wireless module and TE Connectivity Yagi antennas. Two Raspberry Pi 4 Model B units were able to communicate over a distance of 106km between Mount Greylock and Mount [...]
As Arm CEO Rene Haas said on the day of our initial public offering (IPO) one year ago “an IPO is just a moment in time”, with plenty of opportunities ahead to build the future of computing on Arm. Since September 14, 2023, we have moved at pace to fulfil this mission.
Across the entire stack from the foundational technology to the software, Arm has had a profound impact in the past year as a public company. This includes Arm Compute Subsystems (CSS) for multiple markets, the growing influence and adoption of Armv9, new Arm-powered silicon and technologies, rising software capabilities and various announcements and initiatives that showcase our leading role in AI and the global technology ecosystem.
However, this is just the start of our journey as a public company, with plenty of exciting new developments and growth opportunities in the future. This is made possible by our high performance, power-efficient technologies for the age of AI.
Check out our “One Year After the IPO” report below that provides more details about these momentous achievements during the past year.
The EROFS read-only open-source file-system has seen initial patches posted today for beginning to re-implement the C code within the Rust programming language for better safety guarantees and the possibility of more performance optimizations...
Have you ever discovered a cool piece of tech buried in your drawer and thought, “This could make for an awesome project”? That’s exactly what happened to Roni Bandini, maker, writer, electronics artist – and Arduino Alvik Star!
Bandini began coding at 10 years old, and has always found automatons and robots fascinating. About Alvik, he has said, “I really like this little robot—the elegance of its concept and design. As soon as I encountered it, I dove into several projects aimed at expanding its default capabilities.”
One of those projects in particular caught our attention, and we are excited to share it with you.
Getting the building blocks ready
After stumbling upon a tiny Seeed Studio XIAO ESP32S3 with an OV2640 camera sensor, Bandini saw its potential right away. It was the perfect tool to upgrade Arduino’s Alvik robot with computer vision. His mission? To teach Alvik to evade law enforcement officials – or at least a LEGO® police figure!
Since both the Alvik main board and the XIAO cam board use ESP32, Bandini used ESPNow – a fast communication protocol – to connect the camera with the robot. He then 3D-printed two support bars and attached them with a pair of M3 screws.
Learning to react fast!
But before the epic police chase could begin, Alvik needed some training. Bandini took pictures of the LEGO® police figure and a ball and uploaded them to Edge Impulse. He then exported the trained model as an Arduino library using the EON compiler, before importing the zip file into the Arduino IDE.
Once everything was set up and the MicroPython script created, Alvik was ready to roll. As it moved forward, the robot took pictures and processed them through a machine learning (ML) model. If it detected the police figure, Alvik would turn around and flash a red light. In other words, it was time to make a quick getaway!
For more details on this exciting project, including a link to a YouTube demo, visit Bandini’s blog post here.
Making it useful
However, the action doesn’t stop there. Although Alvik can drive autonomously, Bandini has also adapted a remote control from the 1980s to give himself even more control. How? By writing C++ routines that translate the remote’s coordinates into commands. These commands are then sent via ESPNow to the MAC address of the ESP32 in Alvik, where they trigger functions to move the robot.
Inspired by an old-school advertisement for the Omnibot 2000 robot, Bandini has even taught Alvik to bring him a glass of whiskey! While we don’t recommend this for anyone under the legal drinking age, there’s no reason why you can’t substitute it for your favorite refreshments!
Following the weekend news of the AMDGPU kernel driver becoming too large that it's causing the Plymouth boot splash screen on slower Linux systems to time-out, longtime AMD Linux graphics driver engineer Marek Olšák expressed a new idea for helping to reduce some bloat from this AMD kernel graphics driver...
As artificial intelligence (AI) has erupted, Secure by Design for AI has emerged as a critical paradigm. AI is integrating into every aspect of our lives — from healthcare and finance to developers to autonomous vehicles and smart cities — and its integration into critical infrastructure has necessitated that we move quickly to understand and combat threats.
Necessity of Secure by Design for AI
AI’s rapid integration into critical infrastructure has accelerated the need to understand and combat potential threats. Security measures must be embedded into AI products from the beginning and evolve as the model evolves. This proactive approach ensures that AI systems are resilient against emerging threats and can adapt to new challenges as they arise. In this article, we will explore two polarizing examples — the developer industry and the healthcare industry.
Complexities of threat modeling in AI
AI brings forth new challenges and conundrums when working on an accurate threat model. Before reaching a state in which the data has simple edit and validation checks that can be programmed systematically, AI validation checks need to learn with the system and focus on data manipulation, corruption, and extraction.
Data poisoning: Data poisoning is a significant risk in AI, where the integrity of the data used by the system can be compromised. This can happen intentionally or unintentionally and can lead to severe consequences. For example, bias and discrimination in AI systems have already led to issues, such as the wrongful arrest of a man in Detroit due to a false facial recognition match. Such incidents highlight the importance of unbiased models and diverse data sets. Testing for bias and involving a diverse workforce in the development process are critical steps in mitigating these risks.
In healthcare, for example, bias may be simpler to detect. You can examine data fields based on areas such as gender, race, etc.
In development tools, bias is less clear-cut. Bias could result from the underrepresentation of certain development languages, such as Clojure. Bias may even result from code samples based on regional differences in coding preferences and teachings. In developer tools, you likely won’t have the information available to detect this bias. IP addresses may give you information about where a person is living currently, but not about where they grew up or learned to code. Therefore, detecting bias will be more difficult.
Data manipulation: Attackers can manipulate data sets with malicious intent, altering how AI systems behave.
Privacy violations: Without proper data controls, personal or sensitive information could unintentionally be introduced into the system, potentially leading to privacy violations. Establishing strong data management practices to prevent such scenarios is crucial.
Evasion and abuse: Malicious actors may attempt to alter inputs to manipulate how an AI system responds, thereby compromising its integrity. There’s also the potential for AI systems to be abused in ways developers did not anticipate. For example, AI-driven impersonation scams have led to significant financial losses, such as the case where an employee transferred $26 million to scammers impersonating the company’s CFO.
These examples underscore the need for controls at various points in the AI data lifecycle to identify and mitigate “bad data” and ensure the security and reliability of AI systems.
Key areas for implementing Secure by Design in AI
To effectively secure AI systems, implementing controls in three major areas is essential (Figure 1):
Figure 1: Key areas for implementing security controls.
1. Data management
The key to data management is to understand what data needs to be collected to train the model, to identify the sensitive data fields, and to prevent the collection of unnecessary data. Data management also involves ensuring you have the correct checks and balances to prevent the collection of unneeded data or bad data.
In healthcare, sensitive data fields are easy to identify. Doctors offices often collect national identifiers, such as drivers licenses, passports, and social security numbers. They also collect date of birth, race, and many other sensitive data fields. If the tool is aimed at helping doctors identify potential conditions faster based on symptoms, you would need anonymized data but would still need to collect certain factors such as age and race. You would not need to collect national identifiers.
In developer tools, sensitive data may not be as clearly defined. For example, an environment variable may be used to pass secrets or pass confidential information, such as the image name from the developer to the AI tool. There may be secrets in fields you would not suspect. Data management in this scenario involves blocking the collection of fields where sensitive data could exist and/or ensuring there are mechanisms to scrub sensitive data built into the tool so that data does not make it to the model.
Data management should include the following:
Implementing checks for unexpected data: In healthcare, this process may involve “allow” lists for certain data fields to prevent collecting irrelevant or harmful information. In developer tools, it’s about ensuring the model isn’t trained on malicious code, such as unsanitized inputs that could introduce vulnerabilities.
Evaluating the legitimacy of users and their activities: In healthcare tools, this step could mean verifying that users are licensed professionals, while in developer tools, it might involve detecting and mitigating the impact of bot accounts or spam users.
Continuous data auditing: This process ensures that unexpected data is not collected and that the data checks are updated as needed.
2. Alerting and monitoring
With AI, alerting and monitoring is imperative to ensuring the health of the data model. Controls must be both adaptive and configurable to detect anomalous and malicious activities. As AI systems grow and adapt, so too must the controls. Establish thresholds for data, automate adjustments where possible, and conduct manual reviews where necessary.
In a healthcare AI tool, you might set a threshold before new data is surfaced to ensure its accuracy. For example, if patients begin reporting a new symptom that is believed to be associated with diabetes, you may not report this to doctors until it is reported by a certain percentage (15%) of total patients.
In a developer tool, this might involve determining when new code should be incorporated into the model as a prompt for other users. The model would need to be able to log and analyze user queries and feedback, track unhandled or poorly handled requests, and detect new patterns in usage. Data should be analyzed for high frequencies of unhandled prompts, and alerts should be generated to ensure that additional data sets are reviewed and added to the model.
3. Model tuning and maintenance
Producers of AI tools should regularly review and adjust AI models to ensure they remain secure. This includes monitoring for unexpected data, adjusting algorithms as needed, and ensuring that sensitive data is scrubbed or redacted appropriately.
For healthcare, model tuning may be more intensive. Results may be compared to published medical studies to ensure that patient conditions are in line with other baselines established across the world. Audits should also be conducted to ensure that doctors with reported malpractice claims or doctors whose medical license has been revoked are scrubbed from the system to ensure that potentially compromised data sets are not influencing the model.
In a developer tool, model tuning will look very different. You may look at hyperparameter optimization using techniques such as grid search, random search, and Bayesian search. You may study subsets of data; for example, you may perform regular reviews of the most recent data looking for new programming languages, frameworks, or coding practices.
Model tuning and maintenance should include the following:
Perform data audits to ensure data integrity and that unnecessary data is not inadvertently being collected.
Review whether “allow” lists and “deny” lists need to be updated.
Regularly audit and monitor alerts for algorithms to determine if adjustments need to be made; consider the population of your user base and how the model is being trained when adjusting these parameters.
Ensure you have the controls in place to isolate data sets for removal if a source has become compromised; consider unique identifiers that allow you to identify a source without providing unnecessary sensitive data.
Regularly back up data models so you can return to a previous version without heavy loss of data if the source becomes compromised.
AI security begins with design
Security must be a foundational aspect of AI development, not an afterthought. By identifying data fields upfront, conducting thorough AI threat modeling, implementing robust data management controls, and continuously tuning and maintaining models, organizations can build AI systems that are secure by design.
This approach protects against potential threats and ensures that AI systems remain reliable, trustworthy, and compliant with regulatory requirements as they evolve alongside their user base.
Back at FOSDEM in February we showed off how Matrix could be used for E2EE-preserving messaging interoperability as required by the Digital Markets Act messaging interoperability - and we announced that Element had been working with Meta on integrating with its DMA APIs in order to connect WhatsApp to Matrix. You can see the video here, and we also demoed interop working at the technical level to the European Commission a few days beforehand.
Subsequently WhatsApp launched its DMA portal on March 8th, and the proposed Reference Offer (i.e. the terms you have to accept as a Requesting Party in order to interoperate) was revealed. The Reference Offer for Facebook Messenger was launched on September 6th. At the time of the WhatsApp launch we flagged up some significant unresolved questions - the main points being that:
WhatsApp would require their users to manually enable DMA in settings before they can receive any traffic from interconnecting service providers (e.g. Element) - meaning that WhatsApp users would not be reachable by default.
WhatsApp would require the client IP of any interconnecting users, in order to apply ‘platform integrity’ anti-abuse / trust & safety controls.
WhatsApp would not allow an interconnecting service to buffer messages serverside.
WhatsApp would require each Matrix server provider to sign a separate agreement in order to interconnect - i.e. you can’t bridge other server’s users unless those servers have signed a contract with Meta.
Now, the good news is that we’ve subsequently been talking with WhatsApp to see if we could progress these points - and we’re happy to say that they’ve listened to us and we’ve made progress on the first 3 items:
Meta recently shared an update on the messaging interoperability user experience and will allow all EU users to be reachable by interoperable services by default. It’ll also give people the option of how they want to manage their inbox as well as a range of features like read receipts, typing indicators and reactions.
We’ve come up with a plan with WhatsApp to reduce the amount of matrix user data we share with WhatsApp. WhatsApp’s interop solution however, doesn’t yet support multi-device conversations or shared conversation history like normal Matrix, which means that normal Matrix server-side synchronised history won’t work for these conversations.
In terms of not allowing open federation: this looks unlikely to change, given Meta needs to know who is responsible for the servers who connect to them, and ensure they agree to the terms of use as required by DMA.
During discussions, another point came up which we’d previously overlooked: section 7.5.1 of the current reference offer states: “Partner User Location. Any Partner Users that Partner Enlists or provides access to the Interoperable Messaging Services must be located and remain in the EEA”. In other words, interop would only be available to Matrix users physically in the EEA, which is obviously against the Matrix Foundation’s manifesto to provide secure communication to everyone. Moreover, to demonstrate compliance the Matrix side would have to geolocate the client’s IP.
It turns out that this limitation to EU users ended up being the biggest obstacle for productising the native Matrix<>WhatsApp bridge, as it is unclear whether it’s financially viable for anyone (e.g. Element) to launch such a bridge if it only works for Matrix users physically within the EEA (not to mention the costs and privacy issues of geolocating Matrix users).
Now, on one hand, deploying Matrix as a mature standards-based protocol for WhatsApp interop with native E2EE feels like a worthy goal: indeed, it effectively gives DMA interoperators a stable standardised API with pre-existing SDKs to implement against, rather than having to implement against proprietary and potentially shifting vendor APIs. So overall it moves the needle towards the end goal of Matrix’ mission.
On the other hand, this all may be moot if the return on investment of building DMA interop with WhatsApp via Matrix is too far away for any company in the Matrix ecosystem to be able to afford the investment, and if there isn’t an appetite for anyone to fund it. Funding constraints on both the Foundation and the ecosystem today are such that this work will only happen if explicitly sponsored by an organisation who is willing to commit to fund it.
So:if you are an organisation with users in the EU who would like them to interoperate with EU WhatsApp users via Matrix, and have the funds to sponsor development of building out an official production-grade Matrix<->WhatsApp bridge, please get in touch with me.
Alternatively, if the geographic constraints are a showstopper for you, please let us know.
We’re assuming that there may be smaller messaging providers, or domain-specific messaging services who want to connect their end-users through to WA end-users, and may be happy to be constrained to EU geography. However, bridge developers need evidence and financial support to progress this. Meanwhile, if you are interested in the strategic importance of the Digital Markets Act, this is an opportunity to put your money where your mouth is.
While having the Supermicro ARS-211M-NR R13SPD server in the lab for AmpereOne benchmarking with the flagship AmpereOne A192-32X processor, I took the opportunity to run some fresh GCC vs. LLVM Clang compiler performance benchmarks on AArch64. Here are those results for that healthy competition between these open-source C/C++ compilers on AmpereOne cores.
Building off yesterday's Linux 6.11 release, the GNU Linux-libre 6.11-gnu kernel is now available that is the downstream stripping out driver support/features depending upon closed-source microcode/firmware and other modifications in the name of software freedom and ensuring no closed-source bits are used on Linux-libre-enabled systems...
In a previous post-quantum (PQ) article, we introduced the threat that quantum computing presents for any systems, networks and applications that utilize cryptography. In this article, you’ll learn what you can do to assist your organization in achieving crypto-agility with Red Hat and what to expect of Red Hat products as we begin to integrate post-quantum cryptographic functions into them.The capabilities described in the following sections assume timely and functional implementation of industry standards and specifications and the libraries that implement them. If these are not achieved,
Linux 6.11 is out with Linus Torvalds’ announcement on the Linux kernel mailing list (LKML): I’m once again on the road and not in my normal timezone, but it’s Sunday afternoon here in Vienna, and 6.11 is out. The last week was actually pretty quiet and calm, which is nice to see. The shortlog is below for anybody who wants to look at the details, but it really isn’t very many patches, and the patches are all pretty small. Nothing in particular stands out – the biggest patch in here is for Hyper-V Confidential Computing documentation. Anyway, with this, the merge window will obviously open tomorrow, and I already have 40+ pull requests pending. That said, exactly _because_ I’m on the road, it will probably be a fairly slow start to the merge window, since not only am I on my laptop, there’s OSS Europe starting tomorrow and then the [...]
Join us this week as Josepha takes a personal journey down memory lane to her first encounters with WordPress. In this episode, she shares the story of her very first WordPress website, the excitement of getting involved with WordCamps, and how those early discoveries shaped her rewarding path in the WordPress community. Whether you’re a seasoned user or new to the platform, Josepha’s reflections will inspire you with insights from her earliest days in WordPress.
[00:00:00] Josepha: Hello, everyone, and welcome to the WordPress Briefing, the podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go.
[00:00:28] (Music intro)
[00:00:39] Josepha: Folks, this week is WordCamp US, and over the past week or so, I spent a fair amount of time talking to people about that first-time experience. And as with any person who’s talking about their version of a shared experience, I started thinking back to mine.
I think my first experience of WordPress was not typical, though. I had never even heard of WordPress when I first went to a WordCamp. I think, I think most of the time people have heard of it before, but I was just there for the plot. So, like many people in my generation, all of us old people of the internet, I was first online with things like Angelfire and GeoCities.
[00:01:16] Josepha: When I went to college, I was keeping friends and family up to date on what I was up to with a little, like, newsletter? And then Xanga made it to our college campus, and eventually, so did Facebook. And I was one of those kids kind of like half-breaking sites with HTML and CSS I found online. I was changing layouts like every week to suit my mood.
Then, when I graduated and found myself in a city with more talent and more competition than I’d actually accounted for, and started to realize that this online stuff I’d been doing for fun might actually be something that I needed to use as a tool professionally. So, I first went out and reserved my screen name everywhere I could think of.
[00:02:01] Josepha: And we’re talking, like, LiveJournal, WordPress.com, Blogger, all the things, and eventually wound up building my first site on Weebly. And it was super ugly. I’m not able to design things. I have an okay sense for a design that is good, but like, left to my own devices, it’s gonna be what that was, which is like a tie dye background for some reason, and had everything organized into little, like, blocks, I guess? You know, like, old magazine layouts? And it technically had everything that I wanted, but it wasn’t necessarily the best version of any of those things either. I could write a little bit about myself and my services, I could add a few photos, there was a way to contact me, and I could do it all by myself.
And so it was a good place to start. Not long after that, though, I graduated into the need for a more professional-looking website, and it was beautiful. I received a website; someone built it for me. It was beautiful; it had this elegant design. Had a lot of custom functionality, but it was built using ColdFusion. I couldn’t do anything to it. I couldn’t change anything. All minor changes just had to kind of wait until there was enough to make sense to use that maintenance time, that maintenance retainer that I had. It really was just kind of formal. It was an isolated snapshot of all of the sorts of information that was required to be on the web at that time.
[00:03:28] Josepha: And then, later that year, I went to my first WordCamp, and I moved my site over to WordPress. And for the first time, I had that kind of mixture of professional expression that was on top of something that enabled my own expression. And honestly, I didn’t learn much more about the software for a few years. It was doing what I needed it to do, how I needed it to be done, and that’s really what mattered to me.
And when I skip a few years ahead after that, a few years later, when I was learning by organizing Meetups and WordCamps that had speakers that I wanted to hear from, that had topics that I felt like I needed to learn more about, what I remember most about that learning period for me is that I knew that I wasn’t the first person to run into any of my problems, which meant that a solution was probably already out there, and I could find someone to come and teach us about their solution.
[00:04:23] Josepha: And also, I knew that if we were running into a new problem and started breaking things left and right, there was always a way back. I was never really too far away from success. Like I felt like I might be lost, but I still was pretty much findable. And I guess I always want that for new users of the open web now, like new members of our WordPress community.
I want them to feel like the breaking of things is fine and safe and that no mistake is irretrievable. I want us to have some place where perfection isn’t the point. Now listen, I know the software is complex right now. The admin is a little mismatched, your first choices are huge choices, and there are a million places to start.
[00:05:03] Josepha: So, all I can say is, start with what you need, and once you’ve got that, like the back of your hand, move on to what you need next. And keep doing that, bravely and messily, until what you’ve got is all you ever wanted. I’m gonna leave for you, in the show notes, a link to something called WordPress Playground.
It’s gonna launch a little WordPress site in your browser. There will be no host. It’s just all in the browser itself. And it will have the latest bundled theme on it, Twenty Twenty-Four, and the latest version of WordPress. And that’s it. Go in there and click around on the left-hand menu. Start a post, change a page, modify the theme.
Just play around a while. See if it’s something that seems fun to you or valuable, or if it’s something that you can use as a time capsule for your kid because that sounds like a nice little mix of fun and work. And remember, sometimes perfection’s not the point.
[00:05:57] (Music interlude)
[00:06:04] Josepha: That brings us now to our small list of big things.
Folks, as I mentioned at the top, WordCamp US is happening this week. It is September 17th through 20th this year, quite a few more days. But that also means that we’ll have quite a bit more stuff to do. If you have your tickets and haven’t looked at all of the presentations occurring over the four-day event, remember to take a look at the schedule and pick out topics that are interesting. And remember, just because you picked it out before you went doesn’t mean that if you get in there and it doesn’t work for you. You can’t choose a different topic while you’re there. And as a bonus, if this is your first WordCamp that you’ve ever attended, I have you covered. You can check out my previous episode on all the things to remember for your first time attending a WordCamp. And we have a pretty active community as well. If you just have questions or want to get in there and say, ‘Hey, I’m going to a vegan restaurant for lunch; who wants to join me?’ You can do that, and you can definitely find somebody.
Also, there are some upcoming WordPress meetings. So, if you’re not attending WordCamp US but still want to connect with the community, there are a ton of team meetings that are happening. You can find those on make.WordPress.org/meetings, I think. So really, really easy URL to remember. You can join your fellow community members and contribute to the WordPress project there.
[00:07:18] Josepha: And I also wanted to just call your attention to a few really big projects that still need a little bit of help around the project. So, on the one hand, we have Data Liberation. That is still a really big project, but specifically, we are nearly ready to start working on some user-facing elements of that. It is being powered by Playground, and because the data liberation, the migration of one site to another, is so complex, once we get those elements built into Playground, I think it also stands to fix a bunch of the problems that we have across our user flow, our user experience for the project. Things like having better theme previews and being able to get a sense for what a plugin functionally will do for you versus what it says it’s going to do for you. And getting a sense for what the admin looks like, all of those things. And so, anyone who wants to learn more about contributing to Playground or to Data Liberation, I absolutely encourage you to go check out those meetings, see what’s happening, and get your hands a bit dirty with that.
[00:08:26] Josepha: We also have a bunch of stuff happening in our community space. If you had received this podcast from somebody because they were like, hey, I know someone who might like WordPress or who has just learned WordPress and has never been to an event or any other reason that you are listening to this but don’t yet know the community, there is an easier option than just jumping straight into a WordCamp like I did. You can go to a meetup. You can see there’s a widget in your dashboard that’ll tell you what your nearest event is, but if you put your location into that widget, and nothing comes up. Technically, that means that you have an opportunity to bring a bunch of people together to teach you stuff you wish you knew about your site right now. So you can wander over into your dashboard and see those, or you can also head over to the community area on make.WordPress.org and anybody over there is happy to help you get started. And let me tell you, it is a very low-effort sort of thing to do. Here again, perfection’s not the point. And so that, my friends, is your small list of big things.
[00:09:28] Josepha: Don’t forget to follow us on your favorite podcast app or subscribe directly on WordPress.org/news. You’ll get a friendly reminder whenever there is a new episode. If you liked what you heard today, share it with a fellow WordPresser. Or, if you had questions about what you heard, you can share those with me at WPBriefing@WordPress.org. I am your host, Josepha Haden Chomphosy. Thank you for tuning in today for the WordPress Briefing, and I’ll see you again in a couple of weeks. Or tomorrow if we’re all going to WordCamp US.
We’re having a lot of fun with Raspberry Pi Pico 2 in the latest issue of The MagPi. However we didn’t want Raspberry Pi Zero to feel left out. We’ve been using one behind the scenes for extracurricular projects and remembered just how good it was, so we thought we’d highlight some of the best things ever made with it.
NODE Nano Server V2
Plug ‘n’ serve
This upgraded plug-in server works like a lot of modern Wi-Fi boosters where it’s just a plug. It’s very neat. We like it.
magpi.cc/nanoserver2
Penkesu computer
Handheld computing
A very tiny and a very cool looking laptop made with a 7.9”-wide screen and repurposed GBA SP hinges.
magpi.cc/penkesu
ZeroBot
Tiny robot
We had a very similar robot in The MagPi when Raspberry Pi Zero launched, and we still love the form factor.
magpi.cc/zerobot
Simpsons Shuffler
Sitcom randomiser
Ever just wanted to watch a random episode of The Simpsons without getting out your DVDs or scrolling Disney+? Just press that yellow button
magpi.cc/simpsons
GBA Raspberry Pi Zero
Handheld gaming
Hack your old GBA to make it a very comfy and compact handheld gaming system (with an added backlight)
magpi.cc/gbazero
3D printed case
Very cool
This 3D printed and laser-cut case is a very pretty way to not only display your Raspberry Pi Zero but also keep it nice and cool during operation.
magpi.cc/print0case
Zero Drone
Fly high
Lots of folks love making drones with Raspberry Pi, and Raspberry Pi Zero makes it much easier
magpi.cc/zerodrone
Tiny 3D printed Volumio
Walk, man
This is a bit of a mod on some Pimoroni audio add-ons for Raspberry Pi Zero that turn it into your next MP3 player.
magpi.cc/tinyvolumio
My Naturewatch Camera
Critters on camera
This very DIY nature-watching project is a lot cheaper than some, yet can still take some wonderful wildlife photos.
mynaturewatch.net
GamePad Zero
Plug ‘n’ play
One of the first things we did with a Raspberry Pi Zero was glue it into a knock-off USB controller. This project takes it to the next level.
magpi.cc/gamepadzero
The MagPi #145 out NOW!
You can grab the new issue right now from Tesco, Sainsbury’s, Asda, WHSmith, and other newsagents, including the Raspberry Pi Store in Cambridge. It’s also available at our online store, which ships around the world. You can also get it via our app on Android or iOS.
You can also subscribe to the print version of The MagPi. Not only do we deliver it globally, but people who sign up to the six- or twelve-month print subscription get a FREE Raspberry Pi Pico W!
The file structure is one of the most widely-used data structures by Linux kernel drivers. The file struct represents an open file and thus obviously very important and ubiquitous throughout the kernel. With the Linux 6.12 kernel the file struct has been adjusted so it's smaller than before and in turn could help with performance for file-heavy workloads...
Presented earlier this month at the Open-Source Firmware Conference was TamaGo as a means of running Go programming language code bare metal on Arm SoCs as well as eyeing RISC-V too. TamaGo can allow for "0% C and 100% Go code" for ARM/RISC-V device firmware to enhance security...
The Error Detection And Correction (EDAC) driver updates were among the early pull requests submitted for the Linux 6.12 kernel cycle in advance of this week's Linux Kernel Maintainer Summit in Austria. Among the EDAC work this cycle is preparing memory address translation support for future AMD platforms...
Login
