In this age of information which consequently demands the existence of algorithmic mechanisms to funnel relevant information in front of your eyeballs, its incredibly easy to develop tunnel vision and live in an echo chamber, a chamber constantly reverberating your own views. In order to expand one’s belief system, one has to put their System 2 in the driver’s seat and make a conscious effort of pulling the door’s handle and thus exiting the echo chamber.
In an attempt to assimilate the basics of cognitive science, I study the uncharacteristic behaviour of Jim Carrey, a phenomenal method actor, who personates the late Andy Kaufman, a legendary comic, in his biopic, “Man on the Moon” (1999).
Treating the Web as an object or even an actor under the framework of Symbolic Interactionism gives one a voice to articulate and express the symbolic meaning we individuals attach to the Web as an entity, or how it transforms our cognitive abilities once its an active participant in the socialization process.
There are a few more things to cook after our silhouette driver to attain a cheerful face from a successful probe test. We’ll attempt a OF style match of our ADXRS290 device with the skeleton driver, i.e. by creating a device-tree overlay. Configuring our kernel so as to build the drivers/iio/gyro/adxrs290.c module, statically or dynamically, will be explored too. Additionally, kernel practices such as on how to fill the MAINTAINERS document for the automated process of mailing a patch to the maintainers of a driver upstream using ./scripts/get_maintainer.pl, how to create a binding document for the device-tree overlay file, etc. will be covered in this tutorial.
The act of expressing and describing something in rigorous detail usually results in a stronger bond with the artefact one’s attempting to express. But, for me, sometimes the structure of meaning and the association to an idea or to an object seems to break down when you talk about it in an increased verbose manner; it makes complex phenomenons seem very trivial and silly; it unclothes the hidden chauvinistic characteristics; it forces us to look at the “bigger picture”. This, sometimes, is exactly what we need - to step back and truly appreciate and just be aware of things in its naked form.
Carrying on from where we have left Part 1, this post presents the structure of a bare-minimal IIO driver which, when “bound” to our ADXRS290 slave on the SPI master bus, prints a sweet greeting message during its probe() callback.
My take on kicking off writing the driver support for ADXRS290 gyroscope in the Linux kernel is to first sketch an outline of how the driver is supposed to look in the IIO subsystem, the silhouette, and once that is accepted, proceed with “coloring” the intricate details of the driver. Although I assume the reader to be familiar with the Linux Device Model (LDM), I nevertheless drop some resources for the same in this tutorial (?) for the reader to dive into. In this post, I also unravel the ingredients that make up the IIO subsystem in an attempt to reason why it is the suitable home for our gyroscope. Ending the first part, I hypothesize an outline of how the IIO driver support for ADXRS290 would look like.
Here comes the long deferred post briefing on how to setup for an IIO device driver project. Although my setup is specifically targeted for my GSoC project, I think you’d still get a decent idea on how to proceed with your own one. The final (working) setup is achieved using an Ethernet cable (to share the network of the host laptop) to SSH into Raspberry Pi 3B+ running Analog Devices’ Kuiper OS. VNC server and client is additionaly configured to be able to remotely view IIO Oscilloscope’s GUI from the virtual desktop once we have buffer support for our device.
Disclaimer : This article is intended to act as an entry point for beings interested in Linux kernel development and learning about the Linux kernel alongside. I’m aware of numerous such posts on the Internet by kernel veterans but what I intend to bring on the table is the same journey but with a fellow layman, trying to wrap his head around the magnificient piece of art - the Linux kernel - in the hopes of a fun, collaborative approach towards learning.
In this essay, I explore the tightly woven relationship of technology and society with Free and Open Source Software (FOSS) as my technological artefact and the Actor-Network Theory (ANT) as the frame-work of analysis.
This blogpost emphasises on how ‘Selfies’ as digital technologies proliferates and has impact on various sociological abstractions. A theme is chosen under each such abstraction and displayed in the table below:
Technology
Social Relationships
Social Spaces
Concepts
Social Institutions
Selfie
Self
Human Cognition
Prosumption
Economy
Questions are raised and critically analysed using the chosen Technology under each abstraction.
Promising technological advancements in both software and hardware blended with the competitive nature and an immense fan base turned out to be the recipe for the next sports empire - eSports (electronic sports).
Sure, Technology has made our lives easier in almost every aspect; access to resources for gaining knowledge, getting a taxi booked in seconds or even finding “the one” to spend the rest of your life with. But at what cost?
The instant the hunger-clock in my body strikes I see myself reaching for my phone, opening multiple instances of such food-delivery applications and drooling over the deceiving images being portrayed in a linear fashion.
