home.social

Search

1000 results for “0x0”

  1. Finally after several days, I’ve managed to get the start of display initialisation code in for my #PC6502 stack and I can write and read data to/from the display using SPI (65SPI2).

    Console output -

    RUN
    RA8875 INIT:
    CMDWrite>: 0x80 CMD>:0x00
    DATAREAD>: 0x40 Data<:0x75

    Ready

    So the next step is to add in rest of the init code and try to write hellos world on it.

  2. Morgen ist es soweit.
    Um 20 Uhr werde ich den Stream starten, ob wir dann fertig sind oder nicht. Geplant ist aktuell um 20:15 (Ja, die Filmfilm Primetime) zu beginnen.
    Da wir sicherlich wieder das Audiorouting gerade ziehen müssen. Den Stream noch mal umstellen werden und den Chat mitlesen, wird das bestimmt ein coller Abend.

    Seit dabei unter owncast.onpremis.es
    Nur echt mit dem bitsprung
    Dafür steht @[email protected] mit meinem Namen =P

    #zeroday #podcast #0x0d #0d128 #live #stream

  3. Call me weird, but I actually like getting a bluescreen on kernel panics now:

    tux ~ # grep '^CONFIG_DRM_PANIC' /boot/config
    CONFIG_DRM_PANIC=y
    CONFIG_DRM_PANIC_FOREGROUND_COLOR=0xffffff
    CONFIG_DRM_PANIC_BACKGROUND_COLOR=0x0000ff
    CONFIG_DRM_PANIC_SCREEN="kmsg"

    Maybe I should change the background color to 0x0000aa and use a different console font for a more authentic experience, though? 🤔

    #drmpanic #linux #gentoo #kernel #bsod

  4. Call me weird, but I actually like getting a bluescreen on kernel panics now:

    tux ~ # grep '^CONFIG_DRM_PANIC' /boot/config
    CONFIG_DRM_PANIC=y
    CONFIG_DRM_PANIC_FOREGROUND_COLOR=0xffffff
    CONFIG_DRM_PANIC_BACKGROUND_COLOR=0x0000ff
    CONFIG_DRM_PANIC_SCREEN="kmsg"

    Maybe I should change the background color to 0x0000aa and use a different console font for a more authentic experience, though? 🤔

    #drmpanic #linux #gentoo #kernel #bsod

  5. Call me weird, but I actually like getting a bluescreen on kernel panics now:

    tux ~ # grep '^CONFIG_DRM_PANIC' /boot/config
    CONFIG_DRM_PANIC=y
    CONFIG_DRM_PANIC_FOREGROUND_COLOR=0xffffff
    CONFIG_DRM_PANIC_BACKGROUND_COLOR=0x0000ff
    CONFIG_DRM_PANIC_SCREEN="kmsg"

    Maybe I should change the background color to 0x0000aa and use a different console font for a more authentic experience, though? 🤔

    #drmpanic #linux #gentoo #kernel #bsod

  6. Call me weird, but I actually like getting a bluescreen on kernel panics now:

    tux ~ # grep '^CONFIG_DRM_PANIC' /boot/config
    CONFIG_DRM_PANIC=y
    CONFIG_DRM_PANIC_FOREGROUND_COLOR=0xffffff
    CONFIG_DRM_PANIC_BACKGROUND_COLOR=0x0000ff
    CONFIG_DRM_PANIC_SCREEN="kmsg"

    Maybe I should change the background color to 0x0000aa and use a different console font for a more authentic experience, though? 🤔

    #drmpanic #linux #gentoo #kernel #bsod

  7. Sharing my terminal file upload scripts!
    Pick your service, select files with fzf, done. URLs auto-copied to clipboard.
    4 services supported: uguu • 0x0 • catbox • litterbox
    Complete guide: rentry.org/file-upload-scripts

  8. Sharing my terminal file upload scripts!
    Pick your service, select files with fzf, done. URLs auto-copied to clipboard.
    4 services supported: uguu • 0x0 • catbox • litterbox
    Complete guide: rentry.org/file-upload-scripts
    #workflow #automation #bash #fileupload #productivity

  9. Sharing my terminal file upload scripts!
    Pick your service, select files with fzf, done. URLs auto-copied to clipboard.
    4 services supported: uguu • 0x0 • catbox • litterbox
    Complete guide: rentry.org/file-upload-scripts
    #workflow #automation #bash #fileupload #productivity

  10. Sharing my terminal file upload scripts!
    Pick your service, select files with fzf, done. URLs auto-copied to clipboard.
    4 services supported: uguu • 0x0 • catbox • litterbox
    Complete guide: rentry.org/file-upload-scripts
    #workflow #automation #bash #fileupload #productivity

  11. Sharing my terminal file upload scripts!
    Pick your service, select files with fzf, done. URLs auto-copied to clipboard.
    4 services supported: uguu • 0x0 • catbox • litterbox
    Complete guide: rentry.org/file-upload-scripts
    #workflow #automation #bash #fileupload #productivity

  12. Als letzte Option noch die Verbindung eines #Calliopemini 3 über #WebUSB probiert. Formale Kopplung ok:

    const device = await navigator.usb.requestDevice({ filters: [{ vendorId: 0x0D28, productId: 0x0204 }] });

    Beim folgenden await device.open(); kommt jedoch direkt access denied. Alle nachlesbaren Ideen halfen nicht, u. a. mit einem Tool namens »Zadig« WinUSB-Treiber nachzuladen. Fehler bleiben gleich, aber man zerschießt sich damit auch die bisherigen funktionierenden seriellen Zugriffe.

  13. Battery Status:
    Level: 100%
    Raw Level: 95
    Voltage: 4.14V
    Charge Rate: -5.41%/
    Power Source: Connected
    Charging Status: Charge Complete
    Alerts: None
    Status: Hibernating
    Gauge IC: 0x001

    #Preonic

  14. Aufgrund von Gründen bezüglich Planungen und Vorbereitungen für die 0d128 empfehle ich bereits den Account den ich hier im Post referenziert habe, mal zu Folgen.

    Glaubt mir, es wird sich lohnen.

    Auch wenn vorher noch einiges an Vorbereitungen hier zu machen sind, wird dieser Account wichtig werden dafür...

    @Nervofix

    #0d128 #zeroday #podcast #episode #0d #0x0d

  15. Aufgrund von Gründen bezüglich Planungen und Vorbereitungen für die 0d128 empfehle ich bereits den Account den ich hier im Post referenziert habe, mal zu Folgen.

    Glaubt mir, es wird sich lohnen.

    Auch wenn vorher noch einiges an Vorbereitungen hier zu machen sind, wird dieser Account wichtig werden dafür...

    @Nervofix

    #0d128 #zeroday #podcast #episode #0d #0x0d

  16. Oh boi! Looks like on the August my schedule is big :dragnaww:

    1) Speech about #Emacs in SaintP #hackspace (0x08.in/)

    2) Speech about #Xserver (configurarion and hidden gems) in the same hackspace

    3) Speech about my heavily modified #Thinkpad X220 in SaintP area (Roschino town) in #Undefined #hacker festival (undefined.chaosconstructions.r). It will be streamed in the Internet and if I'll be able to obtain a resulting video — I'll upload it to my PeerTube.

  17. #Pico8 #Sizecoding #Postcart
    Nothing special today. Or? Can a simple flower be special?
    --flwr4u!
    function _draw()
    cls(12)
    local size=sin(t()/5)*5
    for ia=0,0x0.ffff,1/7 do
    local d=28+size*2
    local a=ia+t()/4
    circfill(64+cos(a)*d,64+sin(a)*d,15+size,7)
    circ(64+cos(a)*d,64+sin(a)*d,15+size,0)
    end
    circfill(64,64,20+size,14)
    circ(64,64,20+size,0)
    end

  18. 🚐💥 Es geht los! Mein
    Unser Camper-Ausbau startet
    Level 1 – Anmeldung und Abholung
    Zwischen Nervenkitzel, Papierkram und dem ersten echten “Vanlife-Gefühl” war alles dabei 😅

    👉youtu.be/0x0-mFg7JQc

    Kennt das wer auch?
    #vanausbau #campervan #nerdweib #level1 #diycamper #camperstart

  19. SMOLiX CoreWar first steps.

    With just 3 bytes I have:
    - program id (0-1) + opcode (0-15)
    - destination: mode (0-3) + sign (0-1) + value (0-15)
    - source: mode (0-3) + sign (0-1) + value (0-15)

    The IMP warrior is:
    db 0x01, 0x41, 0x40 => MOV $1, $0

  20. So I looked at the #datasheet (https://files.waveshare.com/upload/2/29/7.5inch_e-paper-b-Specification.pdf) to find what I had to do to display some red colour. It seems I have to send 0x04 for each red #pixel, 0x03 for black and 0x00 for white.
    Checked the existing #driver and, sure enough, it sends 0x03 and 0x00! This seems to be the right way.
    [continues]
  21. So I looked at the #datasheet (https://files.waveshare.com/upload/2/29/7.5inch_e-paper-b-Specification.pdf) to find what I had to do to display some red colour. It seems I have to send 0x04 for each red #pixel, 0x03 for black and 0x00 for white.
    Checked the existing #driver and, sure enough, it sends 0x03 and 0x00! This seems to be the right way.
    [continues]
  22. So I looked at the #datasheet (https://files.waveshare.com/upload/2/29/7.5inch_e-paper-b-Specification.pdf) to find what I had to do to display some red colour. It seems I have to send 0x04 for each red #pixel, 0x03 for black and 0x00 for white.
    Checked the existing #driver and, sure enough, it sends 0x03 and 0x00! This seems to be the right way.
    [continues]
  23. So I looked at the #datasheet (https://files.waveshare.com/upload/2/29/7.5inch_e-paper-b-Specification.pdf) to find what I had to do to display some red colour. It seems I have to send 0x04 for each red #pixel, 0x03 for black and 0x00 for white.
    Checked the existing #driver and, sure enough, it sends 0x03 and 0x00! This seems to be the right way.
    [continues]
  24. Swirls for getting better. #pico8 #postcart

    poke(0x5f54,0x60)
    cls(0)
    c={9,8,14,15}
    k=16
    ::_::
    fillp(0)
    sspr(0,0,128,128,48,48,32,32)
    fillp(band(rnd(-1),-1)+0x0.f)
    sspr(4,4,120,120,0,0,128,128)
    for n=1,k do
    p=(n+time())/k circfill(64+32*cos(p),64+32*sin(p),2,c[1+n%#c])
    end
    flip()
    goto _

  25. Gestern beim SFD Tech Treff:
    Analysiere UART Signal beim Midland M-5 CB Funkgerät zwischen Handmike mit Display und Funkgerät.
    0xFE 0x03 0x02 0x09 0x09 ^^

    Ziel: Neues CB Gateway :)

    #cbradio #logicanalyzer #hacking #segfaultdragons #electronics

  26. Jumping in deep immediately

    OS Linux
    Kernel 6.x
    found workaround for hardware errors on critical timer tsc

    snippet from dmesg

    [ 0.000000] tsc: Fast TSC calibration using PIT
    [ 0.000000] tsc: Detected 1796.607 MHz processor

    snippet two

    [ 0.068905] AMD-Vi: Using global IVHD EFR:0x206d73ef22254ade, EFR2:0x0
    [ 0.069804] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    [ 0.074120] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x19e5a467a58, max_idle_ns: 440795257552 ns
    [ 0.074127] Calibrating delay loop (skipped), value calculated using timer frequency.. 3593.21 BogoMIPS (lpj=1796607)
    [ 0.074141] Zenbleed: please update your microcode for the most optimal fix

    line [ 0.074141] clearly states that my microcode is not updated (not related to tsc)

    [ 0.210124] TSC synchronization [CPU#0 -> CPU#8]:
    [ 0.210124] Measured 2808 cycles TSC warp between CPUs, turning off TSC clock.
    [ 0.210126] tsc: Marking TSC unstable due to check_tsc_sync_source failed
    [ 0.210176] #1 #3 #5 #7 #9 #11 #13 #15

    I added tsc=unstable to the boot options in grub, so from what I read here the parameter was passed to the kernel? Can someone please verify for me if this output states that?

    The warning I get is that the BIOS of this machine is broken! and that the option tsc=unstable will work around that massive bug

    #bash #csh #ksh #sh #kernel #parameters #grub #POST #bios #UEFI #Linux #dmesg #Boot #options #programming #POSIX

  27. (continued)
    How I found the Game Genie codes using FCEUX:
    1) By looking at the CHR ROM, I knew I wanted to use tile 0xd2 instead of 0x0a and 0xd7 instead of 0x0e.
    2) I looked at RAM in Hex Editor. A copy of sprite data was at 0x0700-0x07ff. The cursor was in the 2nd sprite slot, so the tile was at 0x0705.
    3) I set a breakpoint on 0x0705 write in Debugger. It found STA $0701,X. The previous instruction was LDA ($00),Y. Whenever that was run, RAM 0x00 contained 0x98 or 0x9d, RAM 0x01 contained 0xd8 and Y was 1, so a byte was being copied to A from RAM 0xd899 or 0xd89e.
    4) Indeed, during gameplay, CPU address 0xd899 contained 0x0a and 0xd89e contained 0x0e.
    5) I used nesdev.org/nesgg.txt to create the codes:
    - XSOSOEZA = "if the CPU tries to read a PRG ROM address that's currently mapped to CPU 0xd899 and contains 0x0a, return 0xd2 instead".
    - NSOSVETA = same but 0xd89e, 0x0e and 0xd7, respectively.
    #NES #gameHacking #GameGenie